Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-8555

not found cache should be expired for packages with implied references from updated package metadata

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.11.2
    • Fix Version/s: 2.11.3
    • Component/s: NPM
    • Labels:
      None
    • Story Points:
      0.5
    • Sprint:
      Sprint 42

      Description

      1. Create an npm proxy repository to the official registry
      2. Request a known package file in the remote registry, through the proxy repository ( not metadata ). This will result in 404. This is as currently designed as Nexus needs package metadata before getting any related package.
      3. request the metadata for the package file in step 2. This is 200 as expected.
      4. request the package that was requested in step 2. This is still 404 not found until an expire cache task on the repository is run or the not found cache expires naturally for the package.

      Expected: When we update the package metadata, the not found cache should be expired for any package referenced in that metadata. Meaning the 404 not found in step 4 above should not require manually expiring cache or waiting until repository configured cache timeout.

        Attachments

          Activity

            People

            Assignee:
            jtom Joe Tom
            Reporter:
            plynch Peter Lynch
            Last Updated By:
            Peter Lynch Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title