You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Bastian Voigt (JIRA)" <de...@tapestry.apache.org> on 2008/02/12 20:31:08 UTC
[jira] Created: (TAPESTRY-2155) HTTP Expires Header incorrect for
static asset resources
HTTP Expires Header incorrect for static asset resources
--------------------------------------------------------
Key: TAPESTRY-2155
URL: https://issues.apache.org/jira/browse/TAPESTRY-2155
Project: Tapestry
Issue Type: Bug
Components: Core Components
Affects Versions: 4.1.3
Environment: Linux, Glassfish 2ur1, SUN JDK 1.6.0_04
Reporter: Bastian Voigt
In AssetService the following assumption is made:
/**
* Time vended assets expire. Since a change in asset content is a change in asset URI, we want
* them to not expire ... but a year will do.
*/
final long _expireTime = _startupTime + 365 * 24 * 60 * 60 * 1000L;
However, this is not entirely true. A change in asset is not always a change in asset URI. This is especially the case for static assets, such as tapestry's core.js or dojo.js. When you upgrade to a new tapestry release, customers always have problems with this. Most of the problems can be solved by having users delete their browser cache, but in large corporate networks with lots of proxies and firewalls things can get more complicated.
Suggested fix:
For static assets, the expire header should not be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org