You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Protocol clients may send protocol requests via the HTTP POST method by including the query directly and unencoded as the HTTP request message body. When using this approach, clients must include the SPARQL query string, unencoded, and nothing else as the message body of the request. Clients must set the content type header of the HTTP request to application/sparql-query. Clients may include the optional default-graph-uri and named-graph-uri parameters as HTTP query string parameters in the request URI. Note that UTF-8 is the only valid charset here.
Hi,
There is an issue when sending an unencoded SPARQL query with
Content-Type: application/sparql-query
. Some characters cause issues then (see below).Because Apache Jena uses this approach for longer query strings it would be very useful if that worked frictionlessly for interoperability.
According to the SPARQL specification
POST with form encoding (works)
curl http://localhost:7001 --data-urlencode 'query=SELECT ?s { ?s a ?o FILTER(true && true)} LIMIT 10'
Direct POST without '&&' (works)
Direct POST with '&&' (fails)
Not sure whether there are further characters that cause problems; in any case there is some issue with encoding/decoding of chars.
The text was updated successfully, but these errors were encountered: