MyBB Internal: One or more warnings occured. Please contact your administrator for assistance.
WebPagetest Forums - Why isn't 301 Cached?

WebPagetest Forums

Full Version: Why isn't 301 Cached?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
In this test result, is hit twice. It is getting a 301 redirect to but on the repeat view, the browser is not using the cached redirect and attempts to hit


Why isn't the cached redirect used on the repeat view? My hunch is that despite the Expires and Cache-Control headers, it is lacking either an E-Tag or Last-Modified header. Is that the case here? Could this be an oversight?

Response headers:
HTTP/1.1 301 Moved Permanently
Content-Type: text/html; charset=UTF-8
Date: Mon, 01 Jul 2013 05:10:44 GMT
Expires: Wed, 31 Jul 2013 05:10:44 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 219
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
What happens in the other browsers?
That's really bizarre. Initially I thought it might be an issue with getting data from dev tools and accidentally showing a request from cache but the timings and tcpdump show that it really is hitting the wire:

and Firefox:

are both caching it as you'd expect.

Going to take some more digging to verify that it isn't something with how WPT runs the tests but it looks like a caching bug in Chrome to me. If so that would be a really good find.
Hey Pat, remember this? I just reran the test and seeing the same results:

Now we have a 301 to www and a 302 to https that are not showing up as cached in the repeat view.
Good question. Needs a little validating to be sure it's not something WPT is doing but looks like a Chrome bug.
Looks like a bug and Canary still has the same issue (Firefox and IE 11 correctly cache it). Just filed a Chrome bug on it:
Reference URL's