[
https://jira.codehaus.org/browse/MJAVADOC-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAVADOC-366.
-----------------------------------
Resolution: Incomplete
Assignee: Robert Scholte
Still missing a usecase where you actually get a {{203}} to confirm it is not
an issue for the javadoc tool. Closing it as {{incomplete}}.
> Unexpected HTTP Status Code For 203 package-list Response
> ---------------------------------------------------------
>
> Key: MJAVADOC-366
> URL: https://jira.codehaus.org/browse/MJAVADOC-366
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.9
> Reporter: James Leigh
> Assignee: Robert Scholte
> Attachments: javadoc-status203.patch
>
>
> JavadocUtil#isValidPackageList is overly quick to discard valid
> package-lists. In particular, it ignores package-list files that return
> status code of 203, which are perfectly fine for JavadocTool.
> Line 1712 should be change to check for status code 203 as shown below.
> {code:java}if ( status != HttpStatus.SC_OK && status !=
> HttpStatus.SC_NON_AUTHORITATIVE_INFORMATION )
> {
> throw new FileNotFoundException(
> "Unexpected HTTP status code " + status + " getting resource " +
> url.toExternalForm() + "." );
> }{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
