[
https://issues.apache.org/jira/browse/JENA-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453144#comment-17453144
]
Andy Seaborne commented on JENA-2203:
-------------------------------------
Interesting -
The java.http was "preview" (=> subject to change) in Java9. It is general
release in Java11 and Jena supports Java11 (and up).
https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/HttpClient.Redirect.html
I don't think 303 itself is a factor. It happens that purl.org does a 301 to
itself and then 303 for the content redirection which is also https->http.
The PR is to change to ALWAYS for Jena 4.3.0 as best compatibility with 4.2.0
and before.
> 303 redirect issues cropped up again in 4.3 snapshot
> ----------------------------------------------------
>
> Key: JENA-2203
> URL: https://issues.apache.org/jira/browse/JENA-2203
> Project: Apache Jena
> Issue Type: Improvement
> Affects Versions: Jena 4.3.0
> Reporter: David Beaudet
> Assignee: Andy Seaborne
> Priority: Major
>
> The same issue noted in #JENA-1263 with 303 redirects not being followed when
> loading ontologies seems to have cropped up again in version 4.3.0 and
> requires the following workaround in client code:
> static {
> HttpEnv.setDftHttpClient(
> HttpClient.newBuilder()
> .connectTimeout(Duration.ofSeconds(10))
> .followRedirects(Redirect.ALWAYS)
> .build()
> );
> The default builder sets Redirect.NORMAL which, at least in the latest
> versions of Java (I'm using OpenJDK 16) doesn't appear to follow 303.
>
> Can reproduce with the following:
> OntModel data =
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM_RULE_INF);
> data.read("http://purl.org/iso25964/skos-thes";);
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
