Tapestry 5
  1. Tapestry 5
  2. TAP5-4

Document the need to version classpath assets to prevent unwanted client browser caching

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.0.16
    • Component/s: None
    • Labels:
      None

      Description

      Because Tapestry now encourages the client browser to cache classpath assets (including tapestry.js, etc.) it is important that when upgrading from one snapshot to another, the browser cache be cleared. It is also possible, in FF, to use shift-reload to force a reload of everything on the page. Otherwise, Taepestry components will references JavaScript functions that do not exist, since the browser is holding on to the older version of the tapestry.js file (because the version number does not change between snapshots).

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development