$smwgSparqlRepositoryConnectorForcedHttpVersion
| 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
Default setting[edit]
$smwgSparqlRepositoryConnectorForcedHttpVersion = false;
This means that CURLOPT_HTTP_VERSION will not be forced for the endpoint communication.
Changing the default setting[edit]
To modify the setting to this configuration parameter, add one of the following lines to your "LocalSettings.php" file after the enableSemantics() call:
- Force 
CURLOPT_HTTP_VERSIONfor 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
See also[edit]
- Help page on using SPARQL and RDF stores
 - Help page on configuration parameter 
$smwgDefaultStoreSets the storage backend to be used for the semantic data 
References
- a b Semantic MediaWiki: GitHub issue gh:smw:1306
 - ^ Semantic MediaWiki: GitHub pull request gh:smw:2044
 - ^ curl.haxx.se:CURLOPTHTTPVERSION
 - ^ CURLOPT_HTTP_VERSION explained