[
https://issues.apache.org/jira/browse/JENA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940393#comment-13940393
]
ASF subversion and git services commented on JENA-656:
------------------------------------------------------
Commit 1579193 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1579193 ]
Improvements for JENA-656
1/ Headers in a defined order, highest q first
2/ Don't include q=1.0
3/ Always ask for something with \*/\*
4/ Encourage efficient forms
> Doesn't send all accepted mime types in header
> ----------------------------------------------
>
> Key: JENA-656
> URL: https://issues.apache.org/jira/browse/JENA-656
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 2.11.1
> Reporter: Natanael Arndt
> Assignee: Andy Seaborne
> Attachments: 0001-Fix-JENA-656.-Improve-mime-type-handling.patch
>
>
> The Jena HTTP query engine doesn't send all the mime types it can process in
> the accept header. It would be better if it could send all of them, so
> services can send a better response.
> Currently the HTTP-Accept-Header claims that jena can only accept
> {{application/sparql-results+xml}} resp. {{application/rdf+xml}} as query
> result. In fact it can process much more types.
> Furthermore some services [1] will return a more general content-type in the
> header when answering a request (e.g. {{application/json}} instead of
> {{application/sparql-results+xml}} or {{application/xml}} instead of
> {{application/rdf+xml}}). It would be good to also try to parse such results
> and to see if the content can be interpreted as SPARQL result.
> [1] http://rdf.myexperiment.org/sparql/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
