hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4042) send Cache-Control header on JSP pages
Date Mon, 22 Oct 2012 23:12:12 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481909#comment-13481909

Alejandro Abdelnur commented on HDFS-4042:

IMO all HTTP responses by Hadoop (web UI, JSON, WebHDFS, HFTP, etc) should set headers to
disable caching because all these resources are dynamic by natur. On WebHDFS and HFTP specifically,
it could be argued that file contents could be cached, but I'd say that proxies will most
likely ignore caching those resources due their size. Not to mentioned security implications,
like permissions.
> 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

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

View raw message