and
chrome and cache gifs, jpgs and css as firefox does? Maybe some obscure
squid ~please-ignore-evil-etag~ header? Or should we migrate to
firefox to use caching?
Thanks!
--
Rodolfo Alcazar Portillo - nosp...@gmail.com
otbits.blogspot.com / counter.li.org
/css
meanwhile chrome -same petition- keeps failing:
1291985161.424 29 127.0.0.1 TCP_MISS/304 340 GET
http://www.elpais.com/css/i_portadillas.css? - DIRECT/62.73.184.40 text/css
Thanks for your time.
--
Rodolfo Alcazar Portillo - nosp...@gmail.com
On Wed, 2010-12-08 at 18:19 +1300, Amos Jeffries wrote:
On 08/12/10 16:51, Rodolfo Alcazar Portillo wrote:
With Firefox, TCP_MEM_HIT:
1291778947.206 0 127.0.0.1 TCP_MEM_HIT/200 626 GET
http://www.elpais.com/css/i_portadillas.css? - NONE/- text/css
...
The VERY SAME PAGE with Google
refresh_pattern ^http: 0 100% 1440 override-expire override-lastmod
reload-into-ims
ignore-reload ignore-no-cache ignore-no-store ignore-must-revalidate
ignore-private
ignore-auth refresh-ims
Thanks!
--
Rodolfo Alcazar Portillo - nosp...@gmail.com
