[ 
https://issues.apache.org/jira/browse/HADOOP-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496883#comment-13496883
 ] 

Eli Collins commented on HADOOP-8998:
-------------------------------------

{quote}
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 nature.
{quote}

Agree.    +1 to the latest patch.
                
> send Cache-Control header on JSP pages
> --------------------------------------
>
>                 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

Reply via email to