[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1867) Fail to set `Last-Modified' HTTP header - content not cached, bad for reverse proxy

[Mike Millson (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1867?page=all ]

Mike Millson updated JBPORTAL-1867:
-----------------------------------

    Help Desk Ticket Reference: https://na1.salesforce.com/50030000004DNFy
                   Description: 

When I request a document from the CMS, there is no HTTP Last-Modified header in the HTTP response.

Therefore, the reverse proxy counts this as a MISS, and fetches the document again.  Local proxies and browser caches will also re-fetch every image on every request.

  was:


When I request a document from the CMS, there is no HTTP Last-Modified header in the HTTP response.

Therefore, the reverse proxy counts this as a MISS, and fetches the document again.  Local proxies and browser caches will also re-fetch every image on every request.


> Fail to set `Last-Modified' HTTP header - content not cached, bad for reverse proxy
> -----------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1867
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1867
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.3 Final
>         Environment: Debian, JBoss 4.2.1.GA
>            Reporter: dpocock
>
> When I request a document from the CMS, there is no HTTP Last-Modified header in the HTTP response.
> Therefore, the reverse proxy counts this as a MISS, and fetches the document again.  Local proxies and browser caches will also re-fetch every image on every request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira