Uploaded image for project: 'Maven Wagon'
  1. Maven Wagon
  2. WAGON-401

Access Denied due to missing User-Agent

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.4
    • 2.6
    • wagon-http
    • None

    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.

      Attachments

        1. accessdenied-test.patch
          1 kB
          Robert Scholte

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. MNG-5509 org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          supercedes

          Improvement - An improvement or enhancement to an existing feature or task. WAGON-230 make it easier to set the HTTP user agent in a configurable way across HTTP wagons, and provide a default for Wagon

          • Major - Major loss of function.
          • Closed

          Activity

            People

              hboutemy Herve Boutemy
              rfscholte Robert Scholte
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: