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

Tapestry may send a 304 response to a browser that has an asset who minimized/non-minimized state does not match the server's configuration

    Details

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

      Description

      When an application is run with minification alternatingly enabled and disabled, it can happen that the browser uses a cached minified asset when minification is actually disabled.
      The problem is that both the minified and un-minified versions of an asset are served from the same URL with the same Last-Modified header.
      The cleanest solution would probably be to serve minified assets from a different URL, like we do for gzipped assets.
      If we don't want to do that, we could also check the Etag in addition to the If-Modified-Since header in the asset request. Currently, if the If-Modified-Since date is after the lastModified date, a 304 is sent regardless of whether the Etags match. However that would mean that the browser could never cache both the minified and the unminified versions of the asset.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              jkemnade Jochen Kemnade
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: