aperez at skarcha
Oct 3, 2009, 3:51 PM
Post #1 of 4
(108 views)
Permalink
|
|
Cache-Control and redundant headers
|
|
Hello!
I've just been playing with Google Page Speed [1], and reading the
documentation I've found this:
"It is important to specify one of Expires or Cache-Control max-age,
and one of Last-Modified or ETag, for all cacheable resources. It is
redundant to specify both Expires and Cache-Control: max-age, or to
specify both Last-Modified and ETag. " [2]
Then, testing with Cherokee, I realize that it's sending redundant headers:
%<------------%<------------%<------------%<------------%<------------
HTTP/1.1 200 OK
Connection: Keep-Alive
Keep-Alive: timeout=15
Date: Sat, 03 Oct 2009 22:48:57 GMT
Server: Cherokee/0.99
Expires: Sat, 26 Dec 2009 22:48:57 GMT
Cache-Control: max-age=7257600
ETag: 4a91cf50=57e
Last-Modified: Sun, 23 Aug 2009 23:22:56 GMT
Content-Type: image/x-icon
Content-Length: 1406
%<------------%<------------%<------------%<------------%<------------
One more thing... Reading this section [3], you can see that
"Cache-Control: public" headers could be interesting.
[1] http://code.google.com/speed/page-speed/index.html
[2] http://code.google.com/intl/en/speed/page-speed/docs/caching.html#LeverageBrowserCaching
[3] http://code.google.com/intl/en/speed/page-speed/docs/caching.html#LeverageProxyCaching
--
Saludos:
Antonio Pérez
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
|
