[JENA-2203] 303 redirect issues cropped up again in 4.3 snapshot

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Jena 4.3.0
• Fix Version/s: Jena 4.3.0
• Assignee: Andy Seaborne
• Reporter: David Beaudet
• Created: 02/Dec/21 19:08
• Updated: 09/Dec/21 10:21
• Resolved: 04/Dec/21 13:07

Description

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");

Issue Links

• is related to: JENA-1263 Configure HTTP client to follow 303 redirects
• links to: GitHub Pull Request #1122