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

Permament move (error 301) not handled properly by Lightweight HTTP Wagon

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0-beta-6
    • Fix Version/s: 2.0
    • Component/s: wagon-http-lightweight
    • Labels:
      None
    • Flags:
      Patch

      Description

      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:

      <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      <html><head>
      <title>301 Moved Permanently</title>
      </head><body>
      <h1>Moved Permanently</h1>
      <p>The document has moved <a href="http://download.java.net/maven/2/org/codehaus/castor/castor-xml-schema/1.2/castor-xml-schema-1.2.pom">here</a>.</p>
      <hr>
      <address>Apache Server at maven2-repository.dev.java.net 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.

        Attachments

        1. mng-4428.patch
          3 kB
          Stephen Compall

          Issue Links

            Activity

              People

              • Assignee:
                struberg Mark Struberg
                Reporter:
                gslowikowski Grzegorz Slowikowski
              • Votes:
                27 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: