Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.9.0
-
2
Description
Nexus 3 does not auto-block on receiving 401 responses from the remote of a proxy repository. Instead, it keeps checking the remote for every inbound request.
This is not consistent with Nexus 2.x, which does auto-block for 401 responses. See NEXUS-6515.
Failure to auto-block on receiving 401 can cause major performance problems, and also has the disadvantage that a user is not alerted to the fact that a proxy repository is not working. It is true that there are cases where you would not want to auto-block on 401, but those are rare, and can be handled by disabling auto-block in the repository's configuration.
2018-03-14 13:18:36,026-0500 WARN [qtp49922574-216] admin org.sonatype.nexus.repository.maven.internal.proxy.MavenProxyFacet - Exception org.sonatype.nexus.repository.proxy.ProxyServiceException: HTTP/1.1 401 Unauthorized checking remote for update, proxy repo ooo failed to fetch foo/bar/maven-metadata.xml with status line HTTP/1.1 401 Unauthorized, content not in cache. 2018-03-14 13:18:41,765-0500 WARN [qtp49922574-63] admin org.sonatype.nexus.repository.maven.internal.proxy.MavenProxyFacet - Exception org.sonatype.nexus.repository.proxy.ProxyServiceException: HTTP/1.1 401 Unauthorized checking remote for update, proxy repo ooo failed to fetch foo/bar/maven-metadata.xml with status line HTTP/1.1 401 Unauthorized, content not in cache. 2018-03-14 13:18:49,982-0500 WARN [qtp49922574-61] admin org.sonatype.nexus.repository.maven.internal.proxy.MavenProxyFacet - Exception org.sonatype.nexus.repository.proxy.ProxyServiceException: HTTP/1.1 401 Unauthorized checking remote for update, proxy repo ooo failed to fetch foo/bar/maven-metadata.xml with status line HTTP/1.1 401 Unauthorized, content not in cache. 2018-03-14 13:19:06,078-0500 WARN [qtp49922574-63] admin org.sonatype.nexus.repository.maven.internal.proxy.MavenProxyFacet - Exception org.sonatype.nexus.repository.proxy.ProxyServiceException: HTTP/1.1 401 Unauthorized checking remote for update, proxy repo ooo failed to fetch foo/bar/maven-metadata.xml with status line HTTP/1.1 401 Unauthorized, content not in cache.
Note: The reproduce case for the above is to create a proxy of https://maven.oracle.com and enter invalid credentials into the authentication settings for it.
Attachments
Issue Links
- causes
-
NEXUS-17548 Docker proxy repositories auto-block for images that don't exist
-
- Closed
-
- is related to
-
NEXUS-4593 Nexus auto-blocks repositories if a request for an artifact fails with access denied (403)
-
- Closed
-
-
NEXUS-9508 Nexus auto-blocks repositories too aggressively
-
- Closed
-
-
NEXUS-17086 Docker proxy auto-blocks when image not found on container-registry.oracle.com
-
- Closed
-
-
NEXUS-6515 Remote returning 401 causes repository to auto-block
-
- Closed
-
-
NEXUS-24731 make the status codes to auto-block proxy repos configurable
-
- New
-