[
https://issues.apache.org/jira/browse/JENA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-510:
-------------------------------
Description:
If I'm not mistaken, when */* content type is used in Accept header, content
negotiation is incorrect. For curl -X GET
http://sparql.org/books/sparql?query=SELECT+*+WHERE+%7B+%3Fs+%3Fp+%3Fo+%7D+LIMIT+1
compare:
{noformat}
application/sparql-results+json =>
application/sparql-results+json
application/sparql-results+json;q=0.1 =>
application/sparql-results+json
*/* =>
application/sparql-results+json
*/*;q=0.1 =>
application/sparql-results+json
application/sparql-results+json;q=0.1, */*;q=0.9 =>
application/sparql-results+json
application/sparql-results+json;q=0.9, */*;q=0.1 => text/csv
application/sparql-results+json;q=0.9, */*;q=0.9 => text/csv
{noformat}
It appears to be that, if the q-value of these two content-types are compared,
the output content-type is incorrect.
Here is an awkward one:
{noformat}
application/sparql-results+xml;q=0.1, */*;q=0.9 =>
application/sparql-results+json
application/sparql-results+xml;q=0.9, */*;q=0.1 =>
application/sparql-results+json
application/sparql-results+xml;q=0.9, */*;q=0.9 =>
application/sparql-results+json
{noformat}
What's going on now?
Just for completeness:
{noformat}
application/sparql-results+xml;q=0.1, application/sparql-results+json;q=0.9
=> application/sparql-results+json
application/sparql-results+xml;q=0.9, application/sparql-results+json;q=0.1
=> application/sparql-results+xml
application/sparql-results+xml;q=0.9, application/sparql-results+json;q=0.9
=> application/sparql-results+json
{noformat}
That looks okay.
was:
If I'm not mistaken, when */* content type is used in Accept header, content
negotiation is incorrect. For curl -X GET
http://sparql.org/books/sparql?query=SELECT+*+WHERE+%7B+%3Fs+%3Fp+%3Fo+%7D+LIMIT+1
compare:
application/sparql-results+json =>
application/sparql-results+json
application/sparql-results+json;q=0.1 =>
application/sparql-results+json
*/* =>
application/sparql-results+json
*/*;q=0.1 =>
application/sparql-results+json
application/sparql-results+json;q=0.1, */*;q=0.9 =>
application/sparql-results+json
application/sparql-results+json;q=0.9, */*;q=0.1 => text/csv
application/sparql-results+json;q=0.9, */*;q=0.9 => text/csv
It appears to be that, if the q-value of these two content-types are compared,
the output content-type is incorrect.
Here is an awkward one:
application/sparql-results+xml;q=0.1, */*;q=0.9 =>
application/sparql-results+json
application/sparql-results+xml;q=0.9, */*;q=0.1 =>
application/sparql-results+json
application/sparql-results+xml;q=0.9, */*;q=0.9 =>
application/sparql-results+json
What's going on now?
Just for completeness:
application/sparql-results+xml;q=0.1, application/sparql-results+json;q=0.9
=> application/sparql-results+json
application/sparql-results+xml;q=0.9, application/sparql-results+json;q=0.1
=> application/sparql-results+xml
application/sparql-results+xml;q=0.9, application/sparql-results+json;q=0.9
=> application/sparql-results+json
That looks okay.
> Incorrect content negotiation with */* in Accept header
> -------------------------------------------------------
>
> Key: JENA-510
> URL: https://issues.apache.org/jira/browse/JENA-510
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ, Fuseki, TDB
> Affects Versions: Jena 2.10.2
> Reporter: Sarven Capadisli
>
> If I'm not mistaken, when */* content type is used in Accept header, content
> negotiation is incorrect. For curl -X GET
> http://sparql.org/books/sparql?query=SELECT+*+WHERE+%7B+%3Fs+%3Fp+%3Fo+%7D+LIMIT+1
> compare:
> {noformat}
> application/sparql-results+json =>
> application/sparql-results+json
> application/sparql-results+json;q=0.1 =>
> application/sparql-results+json
> */* =>
> application/sparql-results+json
> */*;q=0.1 =>
> application/sparql-results+json
> application/sparql-results+json;q=0.1, */*;q=0.9 =>
> application/sparql-results+json
> application/sparql-results+json;q=0.9, */*;q=0.1 => text/csv
> application/sparql-results+json;q=0.9, */*;q=0.9 => text/csv
> {noformat}
> It appears to be that, if the q-value of these two content-types are
> compared, the output content-type is incorrect.
> Here is an awkward one:
> {noformat}
> application/sparql-results+xml;q=0.1, */*;q=0.9 =>
> application/sparql-results+json
> application/sparql-results+xml;q=0.9, */*;q=0.1 =>
> application/sparql-results+json
> application/sparql-results+xml;q=0.9, */*;q=0.9 =>
> application/sparql-results+json
> {noformat}
> What's going on now?
> Just for completeness:
> {noformat}
> application/sparql-results+xml;q=0.1, application/sparql-results+json;q=0.9
> => application/sparql-results+json
> application/sparql-results+xml;q=0.9, application/sparql-results+json;q=0.1
> => application/sparql-results+xml
> application/sparql-results+xml;q=0.9, application/sparql-results+json;q=0.9
> => application/sparql-results+json
> {noformat}
> That looks okay.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
