You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2013/09/11 00:23:52 UTC
[jira] (WAGON-401) Access Denied due to missing User-Agent
[ https://jira.codehaus.org/browse/WAGON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy reopened WAGON-401:
---------------------------------
one use case has been fixed, but there are other in other plugins
IMHO, a default User-Agent should be defined, to reduce the gap between wagon-http and wagon-http-lightweight: not hard to do and will avoid more problems
> Access Denied due to missing User-Agent
> ---------------------------------------
>
> Key: WAGON-401
> URL: https://jira.codehaus.org/browse/WAGON-401
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
> Affects Versions: 2.4
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Critical
> Attachments: accessdenied-test.patch
>
>
> In the last week of August 2013 the policy of Maven Central has been changed. Files like {{maven-metadata.xml}} now require a {{User-Agent}} in their request.
> Otherwise it will fail with an Access Denied status.
> The preferred solution is an adjustment of the policy at Maven Central, but it wouldn't harm if Wagon would set the User-agent.
> The attached could be considered as a smoketest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira