tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-2095) Module assets should not be sent a far-future expires header
Date Thu, 16 May 2013 23:05:16 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-2095.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4
    
> Module assets should not be sent a far-future expires header
> ------------------------------------------------------------
>
>                 Key: TAP5-2095
>                 URL: https://issues.apache.org/jira/browse/TAP5-2095
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Blocker
>              Labels: css
>             Fix For: 5.4
>
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message