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

static css files are not using a cache buster which may cause unexpected UI rendering

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.5.0
    • Fix Version/s: 3.6.0
    • Component/s: UI
    • Labels:
    • Story Points:
      1
    • Sprint:
      Core Sprint 101

      Description

      When you load the Nexus UI, requests are made to URLs like this:

      http://localhost:8081/static/rapture/resources/baseapp-prod_01.css
      http://localhost:8081/static/rapture/resources/baseapp-prod_02.css
      http://localhost:8081/static/rapture/resources/baseapp-prod_03.css

      It seems that the browser will cache these and then during upgrade of Nexus to a new version with the same files, may read the file from the browser cache instead of asking for a new version from Nexus.

      This could lead to artifacts like this:

      Instead of the expected:

      Expected

      The static resource urls should be handled in such a way that makes them unique per Nexus release and so that a user does not need to clear their browser cache to load new UI elements as intended.

      Workaround

      Manually clear your browser cache and restart the browser, then load the new version of Nexus.
       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              cpeters Collin Peters
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Peter Lynch
              Team:
              Nexus - Core
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title