You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Henri Dupre (JIRA)" <ta...@jakarta.apache.org> on 2006/05/28 19:38:30 UTC
[jira] Created: (TAPESTRY-969) add "cache-control" header
add "cache-control" header
--------------------------
Key: TAPESTRY-969
URL: http://issues.apache.org/jira/browse/TAPESTRY-969
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 2.3, 3.0, 3.0.1, 4.0, 3.0.2, 3.0.3, 4.0.1, 4.0.2, 3.0.4
Environment: tomcat
Reporter: Henri Dupre
I hit a major bug with proxies after trying our website with tapestry 4 + friendly URLs. Our ISA server is configured to proxy agressively and as a consequence, tapestry pages got cached although their content is dynamic. After comparing this to another webserver for which the caching did not occur, the other webserver had a "Cache-Control" directive.
I suggest for tapestry to add a "Cache-Control" header equals to "private,no-cache,no-store" when a page is requested and "max-age=3600" for assets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-969) add "cache-control" header
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-969?page=all ]
Jesse Kuhnert resolved TAPESTRY-969.
------------------------------------
Fix Version/s: 4.1
Resolution: Fixed
Check the new @Shell documentation.
> add "cache-control" header
> --------------------------
>
> Key: TAPESTRY-969
> URL: http://issues.apache.org/jira/browse/TAPESTRY-969
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 2.3, 3.0, 3.0.1, 4.0, 3.0.2, 4.0.1, 4.0.2, 3.0.5
> Environment: tomcat
> Reporter: Henri Dupre
> Fix For: 4.1
>
>
> I hit a major bug with proxies after trying our website with tapestry 4 + friendly URLs. Our ISA server is configured to proxy agressively and as a consequence, tapestry pages got cached although their content is dynamic. After comparing this to another webserver for which the caching did not occur, the other webserver had a "Cache-Control" directive.
> I suggest for tapestry to add a "Cache-Control" header equals to "private,no-cache,no-store" when a page is requested and "max-age=3600" for assets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-969) add "cache-control" header
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-969?page=comments#action_12424432 ]
Jesse Kuhnert commented on TAPESTRY-969:
----------------------------------------
I only meant the new "disableCaching" parameter of Shell.
It's going to be impossible for me to come up with a decision on my own for this one. This ticket is good to have for reference, but I'd suggest bringing this up on either the users/dev mailing list to see what others think.
> add "cache-control" header
> --------------------------
>
> Key: TAPESTRY-969
> URL: http://issues.apache.org/jira/browse/TAPESTRY-969
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 2.3, 3.0, 3.0.1, 4.0, 3.0.2, 4.0.1, 4.0.2, 3.0.5
> Environment: tomcat
> Reporter: Henri Dupre
> Fix For: 4.1
>
>
> I hit a major bug with proxies after trying our website with tapestry 4 + friendly URLs. Our ISA server is configured to proxy agressively and as a consequence, tapestry pages got cached although their content is dynamic. After comparing this to another webserver for which the caching did not occur, the other webserver had a "Cache-Control" directive.
> I suggest for tapestry to add a "Cache-Control" header equals to "private,no-cache,no-store" when a page is requested and "max-age=3600" for assets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-969) add "cache-control" header
Posted by "Henri Dupre (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-969?page=comments#action_12424426 ]
Henri Dupre commented on TAPESTRY-969:
--------------------------------------
I know about the @Shell and I implemented this but I think these would be good headers to have by default.
Microsoft IIS + .Net do output these by default. I believe several other web apps do that.
> add "cache-control" header
> --------------------------
>
> Key: TAPESTRY-969
> URL: http://issues.apache.org/jira/browse/TAPESTRY-969
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 2.3, 3.0, 3.0.1, 4.0, 3.0.2, 4.0.1, 4.0.2, 3.0.5
> Environment: tomcat
> Reporter: Henri Dupre
> Fix For: 4.1
>
>
> I hit a major bug with proxies after trying our website with tapestry 4 + friendly URLs. Our ISA server is configured to proxy agressively and as a consequence, tapestry pages got cached although their content is dynamic. After comparing this to another webserver for which the caching did not occur, the other webserver had a "Cache-Control" directive.
> I suggest for tapestry to add a "Cache-Control" header equals to "private,no-cache,no-store" when a page is requested and "max-age=3600" for assets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-969) add "cache-control" header
Posted by "Henri Dupre (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-969?page=comments#action_12424434 ]
Henri Dupre commented on TAPESTRY-969:
--------------------------------------
Ok I'll bring the discussion about the default. The disableCaching is great.
The meta is not enough though to prevent caching on all platforms. ISA Server for instance did not use the meta tag but requires headers on the http response about the cache control. It would be really nice if the parameter on the @Shell could allow to add these http parameters too.
I had to implement a webrequestservicerfilter to do that.
> add "cache-control" header
> --------------------------
>
> Key: TAPESTRY-969
> URL: http://issues.apache.org/jira/browse/TAPESTRY-969
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 2.3, 3.0, 3.0.1, 4.0, 3.0.2, 4.0.1, 4.0.2, 3.0.5
> Environment: tomcat
> Reporter: Henri Dupre
> Fix For: 4.1
>
>
> I hit a major bug with proxies after trying our website with tapestry 4 + friendly URLs. Our ISA server is configured to proxy agressively and as a consequence, tapestry pages got cached although their content is dynamic. After comparing this to another webserver for which the caching did not occur, the other webserver had a "Cache-Control" directive.
> I suggest for tapestry to add a "Cache-Control" header equals to "private,no-cache,no-store" when a page is requested and "max-age=3600" for assets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org