Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.11.4, 3.13.0
Description
This repository returns 404 for requests to the root:
http://jesperpedersen.github.io/fungal/maven2/
But it is a valid repository, for instance, this artifact retrieval works:
I don't see the point of auto-blocking in this case. A 404 from the root doesn't tell us much of anything about whether or not a remote repository is valid, and it isn't hurting Nexus in any way to receive a 404.
Expected
NXRM auto-blocks when:
- 5xx responses from the server
- 401 response
- 407 response
- Exceptions as currently handled.
Attachments
Issue Links
- is duplicated by
-
NEXUS-10100 Proxy automatically blocked when a 409 is received
-
- Closed
-
- is related to
-
NEXUS-13129 proxy repositories with Amazon S3 remotes can be automatically blocked if the Server header value is overridden
-
- Open
-
-
NEXUS-4593 Nexus auto-blocks repositories if a request for an artifact fails with access denied (403)
-
- Closed
-
-
NEXUS-17548 Docker proxy repositories auto-block for images that don't exist
-
- Closed
-
- relates
-
NEXUS-16539 Nexus 3 does not auto-block on 401 responses from https://maven.oracle.com
-
- Closed
-
-
NEXUS-24731 make the status codes to auto-block proxy repos configurable
-
- New
-
-
NEXUS-11403 Detect status of proxy repositories
-
- Refine
-
- mentioned in
-
Page Loading...