How long does Chrome remember a 301 redirect?

Question

I have a new author site that I want to make available from a domain that I had previously used Apache rewriting to bounce traffic to my Amazon site, [R=301,L], which I want to serve up as my own site. I also have a new domain for the interim at least.

Is there (are there) particular durations of times when Chrome in particular will store 301 cached redirects? Some other questions, How long do browsers cache HTTP 301s? and How is 301 redirect implemented by different browsers? , ask, and the answer is given that some browsers do not cache, some cache for the session, and Chrome and IE10 cache in a way that will survive a browser restart, but don't specify how long. Longer than the other browsers tested, but the amount is still unspecified.

So how long does Chrome store a 301 redirect? The questions cited do not specify what it is for Chrome or IE10.

Even if you knew how long it was stored, would you want to rely on it? — Mooseman, Apr 22 '13 at 19:07
Not by choice... but I have an Amazon author site at http://amazon.com/author/cjshayward , which I 301'ed http://cjshayward.com to. I've acquired and am using http://cjsh.name for the new site, also served up as cjshayward.com, and it would be nice to know that after a month the scaffolding domain name can be removed. — Christos Hayward, Apr 23 '13 at 17:34
I'm afraid the answer might be 'until you clear the cache'. If you don't clear the cache, possibly until the heat death of the universe. But I'm not entirely sure. — aditsu quit because SE is EVIL, Nov 18 '13 at 03:00
Please tell chrome we need a way out of this 301 hell hole: https://bugs.chromium.org/p/chromium/issues/detail?id=633023&can=1&q=clear%20301%20redirects&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified — B T, Aug 01 '16 at 02:15
If you use cloudflare or similar service worth noting that also cache header redirects https://support.cloudflare.com/hc/en-us/articles/200168326-Are-301-and-302-redirects-cached-by-Cloudflare- — John Magnolia, Oct 13 '17 at 13:33

score 146 · Accepted Answer · edited Aug 15 '19 at 06:49

146

I resolved this by opening dev tools (F12), click "Network", then click the "Preserve log" checkbox, and make the request that results in the cached 301. Right-click the request that results in the 301 and click "clear browser cache". Try again and then 301 should no-longer be cached.

edited Aug 15 '19 at 06:49

mystic cola

1,465
1
21
39

answered Mar 29 '17 at 13:27

Sam Rueby

5,914
6
36
52

3

That works well. Alternatively, having the `Disable cache` checkbox checked in the dev tools while loading the page also does the trick. – Simon Apr 04 '17 at 12:52
8

`Disable Cache` didn't work for me, had to do what Sam said. – Mohammed Atif Sami Dec 25 '17 at 13:01
For me it was enough just to make request using fetch – piotr_cz Jan 04 '18 at 08:50
`Disable Cache` use to work for me but not anymore I am fairly sure. – johnsnails Feb 15 '18 at 01:55
2

This doesn't actually answer the original question which was "How long does Chrome cache 301 redirects?". – Simon East Apr 19 '18 at 01:49
Worked for me in version 71. Worth noting for the uninitiated that this "preserve log" checkbox is on the "Network" tab of the dev tools window. – mmseng Jan 07 '19 at 18:10
This might also work for other browsers using chromes inspector. I just tested it with qutebrowser. – Lucas Apr 01 '19 at 11:40
"Disable cache" in network only works when dev tool is opened. – Tony Wang Oct 24 '19 at 06:38
Don't work in Version 100.0.4896.88 – Deivydas Voroneckis Apr 20 '22 at 07:54

McGuireV10 · Answer 2 · 2018-12-16T11:20:59.133

53

Go to chrome://net-internals and at the far right open the drop-down and choose "Clear Cache". As of version 48, this was the only thing that worked for me to clear a cached 301.

Update: Unfortunately, as of version 71 (Dec 2018) Google has removed the net-internals feature.

edited Dec 16 '18 at 11:20

answered Jan 29 '16 at 20:34

McGuireV10

9,572
5
48
64

Works on chrome v55 :-) – Elliot Huffman Jan 27 '17 at 17:41
This solution also works on Chrome for Android, where clearing browsing history didn't seem to help at all. – Drew Noakes Sep 11 '17 at 19:42
did not seem to work in Chrome 63.0.3239.132. I had to use the accepted answer. – imjosh Jan 19 '18 at 01:47
Just worked in 64.0.3282.186 (Official Build) (64-bit) – ryanovas Mar 05 '18 at 12:59
Worked on Version 67 – Kareem Jun 07 '18 at 01:40

score 13 · Answer 3 · answered Aug 13 '14 at 13:57

13

The "view-source:"-solution does not work for me in Google Chrome; but using the developer tools and setting "disable cache" to true/checked in the Network-tab forces a re-evaluation. BTW: temporary circumvention can be achieved in an anonymous-session (Ctrl+Shift+N) or by adding some fake query-argument, like "?foo=bar", to the URL.

answered Aug 13 '14 at 13:57

flowtron

854
7
20

1

Thanks - made my day. Strangely, though, this doesn't work for localhost. – Olaf Nov 27 '14 at 16:42
1

Thank you so much, this was driving me mad! @Olaf are you sure? I just used this to stop `http://localhost:8000` from redirecting to `https://localhost:8000` – Dan Passaro Oct 21 '16 at 13:47
At least it didn't work two years ago. Maybe it does now. – Olaf Oct 21 '16 at 14:47

score 4 · Answer 4 · answered Mar 19 '14 at 08:51

4

In either Chrome or Firefox, you can refresh the redirect by typing "view-source:redirect.yoursite.com" and hitting enter. Then, refresh that page. Now, that should force Chrome or Firefox to refresh the redirect.

answered Mar 19 '14 at 08:51

mrbofus

49
2

score 4 · Answer 5 · answered Apr 24 '19 at 11:57

4

The simplest solution to this is to open up F12 dev tools, check disable cache and then visit the place generating the 301 redirect. This should update to the newer version.

answered Apr 24 '19 at 11:57

ocdi

415
4
9

Just tried this and sadly it doesn't work :/. Chrome: 73.0.3683.103 – JohnLBevan Jun 24 '19 at 15:59
@JohnLBevan "Disable cache" in network only works when dev tool is opened. – Tony Wang Oct 24 '19 at 06:38
1

This feature doesn't appear to prevent caching of 301s anymore. Unsure of when it stopped. – Steve Withington Apr 16 '20 at 22:11

score 2 · Answer 6 · answered Apr 29 '20 at 06:27

For example we have cached redirect from http://example.com to https://example.com

Go to Network tools
Check "Preserve log"
Go to http://example.com (it will redirect to https)
Right click on refresh button and click on "Empty cache and Hard Reload"

screenshot

How long does Chrome remember a 301 redirect?

6 Answers6

Linked