Thanks Serge, the document proved to be just what we needed.  We fixed our
issues with a somewhat brain dead proxy as follows
a) making sure Apache was serving documents and images directly (and not
delegating to Resin)
b) Activating mod_expires and using the Expires directives to tell the
stupid proxy to keep images, css and so on in cache for a day
c) Removing a "vary: user-agent" header that was preventing compressed
content from being. We believe this to be a bug in the proxy. Luckily the
largish css and js files we wanted compressed do not vary by user agent.

Jean-François Lamy

-----Message d'origine-----
[mailto:[EMAIL PROTECTED] De la part de Serge Knystautas
Envoyé : 17 mai 2007 13:08
À : General Discussion for the Resin application server
Objet : Re: [Resin-interest] 304 status


This is the best write-up I've seen on how browsers and proxy servers 

resin-interest mailing list

Reply via email to