Handling 304 and header refresh
stockrt at gmail.com
Fri Dec 4 14:04:49 CET 2009
Em 04/12/2009, às 10:10, Daniel Rodriguez <coolbomb at gmail.com>
> I'm also interested in the reason of why it's a bad idea to set a a
> max-age value on a 304 response, and open to any suggestion.
It is not a bad idea. It is, as a matter of fact, recommend by the RFC.
It is just odd that your backend answer with 304 for an unconditional
GET, as Tollef pointed out.
More information about the varnish-misc