Google Chrome; update does not send the If-Modified-Since header
Since I'm currently developing a website that just needs to be able to perform more or less flawlessly under a lot of stress and switch from an automated test case, I would try a simple press-hold-F5 for a few -seconds-in-my-favorite- browser and here I found a strange observation from Google Chrome:
If you do this, Chrome will skip sending the If-Modified-Since header and the web server will be forced to render the page you want to display, resulting in a 200 status code instead of the 304 expected.
In IE8 (and possibly earlier versions) this issue is not .
Try this simple page: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html and then take a close look at the page using Fiddler; weird huh?
My question is, is this by design or a bug from Google?
source to share
This could be a design issue. Browsers often send different requests when updating; for example try pressing CTRL + F5 in IE and you should see IE then make an unconditional HTTP request.
Are you sending the correct HTTP caching directives to your responses so that they aren't checked for freshness? http://www.fiddler2.com/redir/?id=httpperf
source to share
Are you doing Shift-F5 or Ctrl-F5? If so, it will look like that by design . Otherwise it may be a mistake.
source to share