[
https://issues.apache.org/jira/browse/JENA-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103023#comment-16103023
]
ASF GitHub Bot commented on JENA-1378:
--------------------------------------
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/271
JENA-1378 : Set the accept header in the default use case.
...while still respecting any direct HttpClient setup.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena conneg
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/271.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #271
----
commit a89605c150560b42e7d7a46f7d2660678b347ba3
Author: Andy Seaborne <[email protected]>
Date: 2017-07-27T09:10:18Z
Expose the setup of the pooling HttpClientBuilder.
For use by RDFParserBuilder.
commit b11e87393e520815c669bd0086434c2960496b78
Author: Andy Seaborne <[email protected]>
Date: 2017-07-27T09:12:40Z
JENA-1378: Set the accept header in the default use case.
----
> RDFDataMgr does not perform conneg when reading remote RDF resources
> --------------------------------------------------------------------
>
> Key: JENA-1378
> URL: https://issues.apache.org/jira/browse/JENA-1378
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.4.0
> Reporter: Aaron Coburn
>
> In the past, I have been able to use RDFDataMgr.read(Graph, String) to fetch
> vocabularies like so:
> final Graph graph = Factory.createDefaultGraph();
> RDFDataMgr.read(graph, "http://purl.org/dc/terms";);
> This no longer works in 3.4.0. The error is:
> org.apache.jena.riot.RiotException: Failed to determine the content
> type: (URI=http://purl.org/dc/terms/ : stream=text/html)
> The key thing about these remote resources is that they involve content
> negotiation in order to get to the RDF serialization; otherwise an HTML page
> is returned that cannot be parsed by RIOT.
> Adding a Lang attribute to the read() function does not help.
> This appears to be due to the RDFParser library not including an Accept
> header in the HTTP request to the remote resource: https://git.io/v7sTV
> Perhaps a good solution would be to provide a default accept header
> ("text/turtle, application/rdf+xml, application/ld+json") or, even better,
> that accept header could be configurable by a client.
> A work-around for me is to just use the HttpOp.execHttpGet function directly,
> but it would be nice if this functioned as it once did.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
