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
According to the SPARQL 1.1 Protocol, sending a POST request with header Content-Type: application/sparql-query and the SPARQL query as the raw body string should be a supported method. This does not work and fails with the following error log:
Is this because mu-authorization is assuming the POST request's content is always x-www-form-urlencoded?
Expected outcome:
This service should follow the official specification and should at least support all of the described methods. Many clients might follow the official specification and be surprised some of it is not supported, especially since the real supported API is not documented for mu-authorization. A small bit of documentation might also be nice to let clients understand which methods are supported, even if it is supporting the full specification.
The text was updated successfully, but these errors were encountered:
According to the SPARQL 1.1 Protocol, sending a POST request with header
Content-Type: application/sparql-query
and the SPARQL query as the raw body string should be a supported method. This does not work and fails with the following error log:Is this because mu-authorization is assuming the POST request's content is always
x-www-form-urlencode
d?Expected outcome:
This service should follow the official specification and should at least support all of the described methods. Many clients might follow the official specification and be surprised some of it is not supported, especially since the real supported API is not documented for mu-authorization. A small bit of documentation might also be nice to let clients understand which methods are supported, even if it is supporting the full specification.
The text was updated successfully, but these errors were encountered: