[WAGON-401] Access Denied due to missing User-Agent

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.6
• Component/s: wagon-http
• Assignee: Herve Boutemy
• Reporter: Robert Scholte
• Created: 31/Aug/13 12:39
• Updated: 26/Jan/15 04:03
• Resolved: 13/Sep/13 16:12

Description

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.

Update: In the second week of September 2013 the requirement has been reverted.

Issue Links

• is related to: MNG-5509 org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent
• supercedes: WAGON-230 make it easier to set the HTTP user agent in a configurable way across HTTP wagons, and provide a default for Wagon