You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
From:
http://www.the-art-of-web.com/system/mod-pagespeed/#section_3
Instead of returning a 304 Not Modified response, the whole file is transferred
again. So when a user agent makes an If-Modified-Since request, instead of
receiving a 304 Not Modified header, they instead receive the entire file
again. That could increase rather than reduce bandwidth usage in some
situations.
This happens for images when a user hits 'reload' in IE.
Original issue reported on code.google.com by jmara...@google.com on 24 Nov 2010 at 7:39
The text was updated successfully, but these errors were encountered:
Fixed in HEAD.
Resource fetches now support if-modified-since queries. Since rewritten
resources are named by content hash, these queries always report "Unmodified".
Original comment by jmaes...@google.com on 2 Dec 2010 at 4:32
I have a problem with the fix.
On the next scenario the fix makes a problem:
1. asking for a resource.
2. For some reason the resource is not available 404 code will be respond.
3. after 10 minutes our hosting company send if-modified request, but now
instead of retrieve the resource a "unmodified" respond will be sent.
So the resource will be inaccessible for the specific user even if the
temporary problem was resolved.
Original comment by keglevi...@gmail.com on 30 Sep 2014 at 3:04
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Original issue reported on code.google.com by
jmara...@google.com
on 24 Nov 2010 at 7:39The text was updated successfully, but these errors were encountered: