| Status: | effective |
| Progress: | 100% |
| Version: | 2.3.1+ |
| Configuration parameter details:
| |||
| Name | $smwgSparqlRepositoryConnectorForcedHttpVersion | ||
| Description | Sets whether CURLOPT_HTTP_VERSION should explicitly be forced for the endpoint communication |
||
| Default setting |
false
|
||
| (Other) available settings |
|
||
| Software | Semantic MediaWiki | ||
| Since version | |||
| Until version | still available | ||
| Configuration | Store settings | ||
| Keyword | sparqlstore · store · sparql | ||
$smwgSparqlRepositoryConnectorForcedHttpVersion is a configuration parameter that sets whether CURLOPT_HTTP_VERSION should explicitly be forced for the endpoint communication. It was introduced to mitigate errors being encountered as being described in issue #1306.1 The configuration parameter was introduced in Semantic MediaWiki 2.3.1Released on 4 January 2016 and compatible with MW 1.19.0 - 1.25.x..2
$smwgSparqlRepositoryConnectorForcedHttpVersion = false;
This means that CURLOPT_HTTP_VERSION will not be forced for the endpoint communication.
To modify the setting to this configuration parameter, add one of the following lines to your "LocalSettings.php" file after the enableSemantics() call:
CURLOPT_HTTP_VERSION for the endpoint communication$smwgSparqlRepositoryConnectorForcedHttpVersion = true;
This means that CURLOPT_HTTP_VERSION will be forced for the endpoint communication. Options are available as specified at <curl.haxx.se> (CURLOPT_HTTP_VERSION).4
Important Note: Do not change this setting unless you know what you are doing!$smwgDefaultStoreSets the storage backend to be used for the semantic data
