Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-2159

YSlow Recommendation: Version bundled javascript and use far-future expires header

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.10
    • Fix Version/s: 5.0.12
    • Component/s: None
    • Labels:
      None
    • Environment:
      Any

      Description

      Jesse Kuhnert has already implemented this in T4. (Jira issue TAPESTRY-2122.)

      Prevents client side errors that occur if user doesn't flush browser's cache between Tapestry upgrades. (And javascript has changed.)

      See: http://developer.yahoo.com/performance/rules.html#expires

      This really applies to classpath resources. Context resources can also be versioned and (via some kind of servlet container ju-ju) hack the expires header ... but that's an application development and deployment issue seperate from Tapestry.

      Part of this requires that the Tapestry release number be available and incorporated into the mapped path for the classpath asset. See TAPESTRY-2231.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              9902468 Ville Virtanen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: