maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <>
Subject [jira] (MNG-5238) 301, ReasonPhrase:Moved Permanently
Date Sat, 18 Feb 2012 14:56:02 GMT


Olivier Lamy commented on MNG-5238:

maybe but I need more informations.
And according to http spec:
Section 10.3.2 301 Moved Permanently
??If the 301 status code is received in response to a request other than GET or HEAD, the
user agent MUST NOT automatically redirect the request.??
So I add can some flag to say "followMoved" but I understand it doesn't work.
Maybe (certainly) you have a http server in the middle which do redirect permanent. (again
I don't know your infra).
Check that if you have a directive "Redirect permanent" rather than "Redirect".
> 301, ReasonPhrase:Moved Permanently
> -----------------------------------
>                 Key: MNG-5238
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Deployment, Errors, Plugins and Lifecycle
>    Affects Versions: 3.0.4
>         Environment: Continuum 1.3.6, Archiva 1.1.2 
>            Reporter: Lionel Champalaune
> I was in Maven 2.0.9 until two weeks ago.
> I did integration test with maven 3.0.3 and everything was working fine.
> When I decided to migrate my integration system this week I upgrade to 3.0.4 and then
the clean deploy failed with this error:
> Could not transfer artifact groupe:artifact:pom:0.5.0-20120203.164640-2 from/to snapshots
( Failed to transfer file:
Return code is: 301, ReasonPhrase:Moved Permanently
> I don't know how to investigate the problem because it's working with 3.0.3 (Wagon enhancement
> I migrate to 3.0.3 but I think it's better to be with the last version.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message