activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Micó (JIRA) <j...@apache.org>
Subject [jira] [Commented] (APLO-300) Caching issues on activemq.apache.org/apollo website
Date Fri, 22 Mar 2013 12:45:39 GMT

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

José Micó commented on APLO-300:
--------------------------------

A simple workaround is to add a meta tag to the <head> section of the main template
for the website: 

<meta http-equiv="Cache-Control" content="max-age=3600, must-revalidate" />

This will tell the browser to revalidate cached html content after one hour.
The downside of this technique is that meta headers does not control the caching of images
and css.

                
> Caching issues on activemq.apache.org/apollo website
> ----------------------------------------------------
>
>                 Key: APLO-300
>                 URL: https://issues.apache.org/jira/browse/APLO-300
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-website
>    Affects Versions: 1.6
>         Environment: Firefox 19
>            Reporter: José Micó
>            Assignee: Hiram Chirino
>            Priority: Minor
>
> I've noted that after releases I keep seeing the old version of the website, unless I
force a refresh. The old website remains locally cached up to a week, with some pages belonging
to 1.6 and others to 1.5. 
> I've verified that there is no request being performed to the server. This is caused
by the absence of a cache-control header, causing firefox to determine the freshness of cached
pages as the value of the "Date" header minus the value of the "Last-modified" header divided
by 10 (see http://www-archive.mozilla.org/projects/netlib/http/http-caching-faq.html and http://tools.ietf.org/html/rfc2616#section-13.2.4)
. With a new release every two months, that calculation gives 6 days.
> So I suggest to add a header like "Cache-control: max-age=86400" to force daily revalidation
against server (then, most of responses will be 304 Not Modified).
> These are the headers of my local cache entry for http://activemq.apache.org/apollo/documentation/migration-guide.html,
before forcing reload (note the "Last-Modified: Fri, 14 Dec 2012" and "expires: 2013-03-04"):
> (local cache) last fetched: 	2013-02-25 22:11:03
> (local cache) last modified: 	2013-02-25 22:04:08
> (local cache) expires: 	2013-03-04 10:22:34
> response-head: 	HTTP/1.1 200 OK 
> Date: Mon, 25 Feb 2013 07:34:43 GMT 
> Server: Apache/2.4.3 (Unix) OpenSSL/1.0.0g 
> Last-Modified: Fri, 14 Dec 2012 21:36:09 GMT 
> Etag: "ee1-4d0d6d1d80348-gzip" 
> Accept-Ranges: bytes 
> Vary: Accept-Encoding 
> Content-Encoding: gzip 
> Content-Length: 1656 
> Content-Type: text/html; charset=utf-8
> And after forcing reload:
> (local cache) last fetched: 	2013-02-25 22:13:34
> (local cache) last modified: 	2013-02-25 22:13:22
> (local cache) expires: 	2013-02-25 22:19:54
> response-head: 	HTTP/1.1 200 OK 
> Date: Tue, 26 Feb 2013 01:13:22 GMT 
> Server: Apache/2.4.3 (Unix) OpenSSL/1.0.0g 
> Last-Modified: Tue, 26 Feb 2013 00:08:01 GMT 
> Etag: "ee1-4d69573655211-gzip" 
> Accept-Ranges: bytes 
> Vary: Accept-Encoding 
> Content-Encoding: gzip 
> Content-Length: 1659 
> Content-Type: text/html; charset=utf-8

--
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

Mime
View raw message