I’m hitting a strange issue where following an upgrade from 3.58.1 → 5.59.0 I cannot access my docker repo. Reverting back to 3.58.1 all works again. My repo is configured to use a specific port and uses an apache reverse proxy. Bypassing the proxy does nothing to change the outcome, so the issue is clearly within nexus.
To test I’m hitting my server with curl and I’m expecting 404 response (invalid URL - this is my test), as you can see following the upgrade, I get a response from Jetty(9.4.51.v20230217), not Nexus/3.59.0-xx (OSS) as you’d expect?
3.58.1 (working request), ie I get an expected (404) response from Server: Nexus/3.58.1-02 (OSS)
$ curl -I http://192.168.200.111:58001/repository/mydocker/ HTTP/1.1 404 Not Found Server: Nexus/3.58.1-02 (OSS) X-Content-Type-Options: nosniff Content-Security-Policy: sandbox allow-forms allow-modals allow-popups allow-presentation allow-scripts allow-top-navigation X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store, max-age=0, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Expires: 0 X-Frame-Options: DENY Content-Type: text/html Content-Length: 1518
3.59.0 (broken), ie I get an unexpected (400) response from Server: Jetty(9.4.51.v20230217)
curl -I http://192.168.200.111:58001/repository/mydocker/ HTTP/1.1 400 Bad Request Cache-Control: must-revalidate,no-cache,no-store Content-Type: text/html;charset=iso-8859-1 Content-Length: 503 Server: Jetty(9.4.51.v20230217)