Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.11.1
-
None
-
1
-
Sprint 36, Sprint 37
Description
Prints a concerning log message stating "failed content integrity validation" when in actual fact, the remote may have responded with 404 or other implied 'not found' status code.
Instead, print a log message indicating the status code and more exact reason the file was detected as not valid.
To reproduce:
- Change logging level of ROOT to DEBUG
- Request a file through a Maven proxy repository that the remote will return 404 for.
- examine the logs for the message "failed content integrity validation"
Attachments
Issue Links
- is caused by
-
NEXUS-8080 concurrent request paths cause ItemNotFoundException during population of not found cache
-
- Closed
-