Joshua Slive escribió:
Interesting. If what you say is true, then it's a bug in apache, and
perhaps one that will be very difficult to fix. You should report it
to the bug database. The problem might be that the 304 response
doesn't contain a content-type header and therefore can't be activate
enough, because it seems that Firefox doesnt
take into account this header if response code is 304. It set 1970 as
new expiry date no matter the value in this header.
Joshua Slive escribió:
On 7/23/07, Bello Martinez Sergio <[EMAIL PROTECTED]> wrote:
- Headers request/response after expi
ime' (sorry if these
titles are not correct, I'm using an Spanish IE and I've transate them
directly)
Thanks,
Sergio
Joshua Slive escribió:
On 7/23/07, Bello Martinez Sergio <[EMAIL PROTECTED]> wrote:
Thanks again, Joshua.
You are right, it's my application tha
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
Thanks,
Sergio
Joshua Slive escribió:
On 7/23
7;d like: instead of this, entity's
expiry date are updated to '1970-01-01 01:00:00', so the result is the
same, each time the browser needs one of these elements, we have a
request-304 response (with a worse performance)
Joshua Slive escribió:
On 7/20/07, Bello Martinez Sergio
Hi all,
I've configured Apache so that some elements (i.e. .js, .gif, .jpeg,
etc) are stored in browser's cache during a time. When I access to a
page contaning any of those elements, the browser doesn´t make a request
to the server, it get the content from cache instead. Until this moment,
al
