Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.11.1
-
2
-
Sprint 36, Sprint 37
Description
Create a npm hosted repo with id 'npm-hosted'.
Publish one package into it.
Hit the /-/all resource for this repo. Verify the published package metadata.
Delete the entire npm hosted repo using the repository Delete button.
Create another npm hosted repo with the same id.
Hit the /-/all resource for this repo again - you still get metadata about the first repo even though the new repo contains nothing.
Similar:
delete all the content from a hosted npm repo but leave the repo itself. Nexus still serves metadata about packages which do not exist. Expire cache on the hosted repo does not help.
Attachments
Issue Links
- fixes
-
NEXUS-8290 npm proxy attempts network access when in blocked state, results in 500 response
-
- Closed
-
- relates
-
NEXUS-8063 expired caches and metadata not updated for npm proxy repos
-
- Closed
-