You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2012/10/12 15:37:08 UTC
[jira] [Commented] (HDFS-4042) send Cache-Control header on JSP
pages
[ https://issues.apache.org/jira/browse/HDFS-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474985#comment-13474985 ]
Steve Loughran commented on HDFS-4042:
--------------------------------------
Looks like a duplicate of https://issues.apache.org/jira/browse/HADOOP-6607
Big issue: how to fix: per servlet or with a filter -and if a filter is used, what impact does that have on things like webhdfs.
Note that it's traditional to add some other headers, HADOOP-6607 states them; the expires: flag ensures that it isn't cached on the client either, the other two to stop proxies of various sorts from caching them
> send Cache-Control header on JSP pages
> --------------------------------------
>
> Key: HDFS-4042
> URL: https://issues.apache.org/jira/browse/HDFS-4042
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node, name-node
> Affects Versions: 2.0.2-alpha
> Reporter: Andy Isaacson
> Priority: Minor
>
> 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