You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/11/14 07:22:12 UTC
[jira] [Updated] (HADOOP-8998) set Cache-Control no-cache header on
all dynamic content
[ https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated HADOOP-8998:
---------------------------------------
Summary: set Cache-Control no-cache header on all dynamic content (was: send Cache-Control header on JSP pages)
> set Cache-Control no-cache header on all dynamic content
> --------------------------------------------------------
>
> Key: HADOOP-8998
> URL: https://issues.apache.org/jira/browse/HADOOP-8998
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.0.2-alpha
> Reporter: Andy Isaacson
> Assignee: Alejandro Abdelnur
> Priority: Minor
> Attachments: HADOOP-8998.patch, HADOOP-8998.patch
>
>
> We should send a Cache-Control header on JSP pages so that HTTP/1.1 compliant caches can properly manage cached data.
> Currently our JSPs send:
> {noformat}
> % curl -v http://nn1:50070/dfshealth.jsp
> ...
> < HTTP/1.1 200 OK
> < Content-Type: text/html; charset=utf-8
> < Expires: Thu, 01-Jan-1970 00:00:00 GMT
> < Set-Cookie: JSESSIONID=xtblchjm7o7j1y1f33r0mpmqp;Path=/
> < Content-Length: 3651
> < Server: Jetty(6.1.26)
> {noformat}
> Based on a quick reading of RFC 2616 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html I think we want to send {{Cache-Control: private, no-cache}} but I could be wrong. The Jetty docs http://docs.codehaus.org/display/JETTY/LastModifiedCacheControl indicate this is fairly straightforward.
--
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