Handling 304 and header refresh

[Tollef Fog Heen]

]] Daniel Rodriguez 

| You are right, in the second request there is no "If-Modified-Since"
| in the communication between the varnish-backend, but between the
| client-varnish there is a  "If-Modified-Since" (this can be verified
| in the varnish logs attached before), so varnish some how is asking
| for a unconditional GET, and ignoring the "If-Modified-Since", like
| Tollef also stated in a later reply to this thread

Varnish doesn't do conditional GETs to the backend, so this is perfectly
normal.

| On Thu, Dec 3, 2009 at 9:04 AM, Tollef Fog Heen
| <tfheen at redpill-linpro.com> wrote:
| > ]] Daniel Rodriguez
| [...]
| > Your backend seems to reply with 304 to an unconditional GET request,
| > which is quite odd.
| 
| So there is no way to get this to work as as i want?.

What do you want?  A 304 response is not a valid response to an
unconditional GET.

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

As Rogerio Schneider points out, it's not.

-- 
Tollef Fog Heen 
Redpill Linpro -- Changing the game!
t: +47 21 54 41 73