maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Compall (JIRA)" <>
Subject [jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven
Date Thu, 04 Mar 2010 21:43:55 GMT


Stephen Compall commented on MNG-4428:

The underlying cause seems to be wagon-http-lightweight's reliance on HttpURLConnection's
redirect behavior.  One should first note that *all* the problematic redirects in question
are cross-protocol, i.e. https->http or vice versa.

Then, consider, which always returns
false (don't follow) when the protocol of the old URL doesn't match that of the new one. 
See line 1830 in openjdk-6-src-b18-16_feb_2010 for the specifics.

Many thanks to John Raymond Wold for figuring out why the HttpURLConnection wasn't redirecting.

> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>                 Key: MNG-4428
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.2.1
>            Reporter: Grzegorz Slowikowski
>            Priority: Minor
> Artifact cannot be downloaded by http-lightweight-wagon used (as default) in all Maven
versions except 2.2.0, which uses http-wagon by default.
> Instead of pom and jar files html files appear in the local repo with content like:
> <html><head>
> <title>301 Moved Permanently</title>
> </head><body>
> <h1>Moved Permanently</h1>
> <p>The document has moved <a href="">here</a>.</p>
> <hr>
> <address>Apache Server at Port 443</address>
> </body></html>
> Only Maven 2.2.0 handles 301 properly.
> By the way, I haven't expected such Apache configuration (permament move) in central
Maven repo.
> As you can see this is not handled properly by almost all versions of Maven.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message