[
http://jira.codehaus.org/browse/WAGON-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved WAGONHTTP-15 to WAGON-123:
---------------------------------------------
Affects Version/s: (was: 1.0-beta-1)
Key: WAGON-123 (was: WAGONHTTP-15)
Project: Maven Wagon (was: wagon-http)
> 302 responses when downloading metadata vid HTTP not handled correctly
> ----------------------------------------------------------------------
>
> Key: WAGON-123
> URL: http://jira.codehaus.org/browse/WAGON-123
> Project: Maven Wagon
> Issue Type: Bug
> Reporter: Petter Måhlén
> Assignee: Brett Porter
>
> We are trying the following setup:
> - Artifactory as a local repository, running in Tomcat
> - Apache mod_proxy_ajp forwarding to Tomcat
> - HTTPS access to the local repository
> When, due to a misconfiguration, Maven tried to fetch data via HTTP rather
> than HTTPS, the Apache server responded with 302 Found, pointing at the HTTPS
> location of the data. This worked for .jar and .pom files, but for metadata
> files, the response was simply saved as it was (an HTML document saying that
> the data was found elsewhere, not an XML document with metadata). This led to
> problems later on in the execution of the Maven client.
> Proposed solution: either consider 302 errors to be errors, and flag that to
> the user, or, alternatively, act as a web browser and follow the forward to
> the correct location of the data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
