Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-2095

Module assets should not be sent a far-future expires header

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 5.4
    • Fix Version/s: 5.4
    • Component/s: tapestry-core
    • Labels:

      Description

      Modules should no longer include either the application version number in the URL, or include a far-future expires header. Instead, module requests and response should support HTTP Etags (http://en.wikipedia.org/wiki/HTTP_ETag).

      The reasoning behind abandoning the application version number is that it relies on the developer to know when to change the version number (well, basically on every redeployment), and it invalidates all assets (this it the case in Tapestry 5.3).

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: