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

Docker proxy repository returns 502 when remote returns 401

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.29.2
    • Fix Version/s: 3.37.0
    • Component/s: Docker
    • Labels:
    • Story Points:
      3
    • Sprint:
      NXRM MadMax Sprint 20, NXRM MadMax Sprint 21
    • Notability:
      4

      Description

      A docker proxy repository returns a 502 response when its remote returns a 401. Normally for proxy repositories this would be working by design, a 401 response indicates a problem with the proxy repository's configuration.  However, docker registries rather unfortunately return 401 when they should be returning 404.  So this means a proxy repository will be returning 502 constantly, and a remote Nexus Repo instance that proxy's the proxy will auto-block.

       

      Expected:  Sadly, docker registries break HTTP protocol here, but we can't fix them, so we will need to fix Nexus Repo.  Docker proxy repositories should not auto-block if the remote returns a 401, and we should return a 404 response from the proxy repository.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mlukaretkyi Maksym Lukaretkyi
              Reporter:
              rseddon Rich Seddon
              Last Updated By:
              Maksym Lukaretkyi Maksym Lukaretkyi
              Team:
              NXRM - Mad Max
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title