On 7/23/07, Bello Martinez Sergio <serbel@xxxxxxxxxx> wrote:
Thanks again, Joshua. You are right, it's my application that set 'must-revalidate' header. But it's not the problem, I've deleted it and all works exactly the same. I suspect the 304 return code is the reason because Firefox set '1970-01-01 01:00:00 (already expired)" expiry date, and not that header. I've found a "half-solution". If I use a 'Header append Cache-Control "max-age=something"' , Apache inserts this header in response, even if return code is 304 (until now I've used only 'ExpiresByType' to set cache-related headers). In this case, if Internet Explorer 6.0 receives max-age header, it updates correctly cache-entry expiry time, but Firefox still updates it to '1970-01-01 01:00:00 '. I'll search a litte more....
I'd like to see full request/response headers for these cases (original and 304), because I can't really believe that MSIE and firefox are broken enough to not properly update their cache on a 304 in the typical case. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|