[jira] [Assigned] (JENA-1263) Configure HTTP client to follow 303 redirects

["A. Soroka (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JENA-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

A. Soroka reassigned JENA-1263:
-------------------------------

    Assignee: A. Soroka

> 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:
> Model m = createDefaultModel();
> RDFDataMgr.read(m, "http://purl.org/dc/terms/");
> org.apache.jena.riot.RiotException: Failed to determine the content type: (URI=http://purl.org/dc/terms/ : stream=text/html)
> A work-around is to add a static block with a custom HTTP client like so:
> static {
>     HttpOp.setDefaultHttpClient(HttpClientBuilder.create().setRedirectStrategy(new LaxRedirectStrategy()).build());
> }
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)