[
https://issues.apache.org/jira/browse/JENA-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15674472#comment-15674472
]
A. Soroka commented on JENA-1263:
---------------------------------
Actually, avoiding the one-use clients would also clean up some of the rest of
the ode relating to not shutting down clients before streams they have
retrieved have been consumed.
> Configure HTTP client to follow 303 redirects
> ----------------------------------------------
>
> Key: JENA-1263
> URL: https://issues.apache.org/jira/browse/JENA-1263
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 3.1.1
> Reporter: Aaron Coburn
> Assignee: A. Soroka
> Priority: Minor
> Fix For: Jena 3.2.0
>
>
> When calling RDFDataMgr.read(Model model, String uri), the underlying HTTP
> client does not appear to follow 303 redirects. For example:
> {code:java}
> Model m = createDefaultModel();
> RDFDataMgr.read(m, "http://purl.org/dc/terms/";);
> {code}
> {code}
> org.apache.jena.riot.RiotException: Failed to determine the content type:
> (URI=http://purl.org/dc/terms/ : stream=text/html)
> {code}
> A work-around is to add a static block with a custom HTTP client like so:
> {code:java}
> static {
> HttpOp.setDefaultHttpClient(
> HttpClientBuilder.create().setRedirectStrategy(
> new LaxRedirectStrategy()).build());
> }
> {code}
> By default the Apache HTTP client follows 301 and 302 redirects (but not 303
> redirects), but the W3C recommends using 303 redirects for publishing RDF
> vocabularies (https://www.w3.org/TR/swbp-vocab-pub/), which is what the
> Dublin Core vocabularies use.
> This sort of redirect handling worked previously, e.g. Jena 3.1.0; it would
> be convenient if the underlying HTTP client simply followed the 303 redirects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
