Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-17296

legacy URLs do not work with nexus.view.exhaustForAgents property

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.7.0, 3.10.0
    • Fix Version/s: 3.13.0
    • Component/s: Transport
    • Labels:
    • Story Points:
      1

      Description

      In 3.10.0, set these in etc/nexus.properties:

      org.sonatype.nexus.repository.httpbridge.internal.HttpBridgeModule.legacy=true
      nexus.view.exhaustForAgents=Apache-Maven.*|Apache Ivy.*|maven-artifact.*
      

      This request will be exhausted by the ExhaustRequestFilter filter:

      curl -v -X PUT http://localhost:8081/repository/maven-releases/foo -H "user-agent: maven-artifact" -o /dev/null

      This request will not and fail as per scenarios described in https://issues.sonatype.org/browse/NEXUS-10234 :

      curl -v -X PUT http://localhost:8081/content/repositories/maven-releases/foo -H "user-agent: maven-artifact" -o /dev/null

      Debugging shows that the filter still has the default agent pattern of Apache-Maven.* for legacy URLs instead of the one set by the property.

      Expected

      Legacy URLs should be perform identically to the regular URLs in the described case.

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jbryan Jeremy Bryan
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Peter Lynch
              Team:
              Nexus - Core
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title