Thanks for the report, marking as Untriaged and requesting Dev team to check the issue and update.

This issue is behind http://stackoverflow.com/questions/16154672/how-long-does-chrome-remember-a-301-redirect?noredirect=1#comment64759764_16154672. Copying and pasting my basenote:


5
down vote
favorite
2
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.

I'm not sure how we'd expose a setting just to clear redirects; it seems like we could end up with a million "fix this particular incorrect kind of cache entry" buttons.

I'm not marking it WontFix myself, but I expect the eventual answer will be "you just need to clear your entire cache".

The browser should at least "Flush" the re-direct when it detected a "re-direct loop"
If the browsers currently has a cached 301 redirect and the site your redirecting to sends it back, you run into this (even though the original redirect is gone.

This hosting nightmare
Previous provider had 301 redirect of https -> http
new provider has redirect of http -> https
Any visitors that had previously visited site now get "redirect loop"

I argue that adding 301 caching to the browser broke expected behaviour for me, so I would expect a feature flag to turn it off.   With this change, I am no longer able to use chrome to do my day job effectively, and will have to migrate to Firefox. 

caching 301 redirects in the browser essentially breaks the ability of servers to set and unset redirects. This cost me an entire day of what should have been productive work. 

There is a way to clear the 301s, as follows:

To clear a permanent redirect in the browser cache, go to chrome://net-internals and at the far right open the drop-down and choose "Clear Cache". 

I have tried every possible fix like comment #9, hard reload, clearing cache, and nothing works.  Once the localhost redirect is in chrome it seems to be there forever.  THIS IS AN ACTUAL BUG!

Is there any way to manually remove these cache entries (without clearing cache completely, which is really annoying).

At least it should be possible to blacklist certain domains/ip-addresses (and localhost/127.0.0.1 should be blacklisted by default) from caching redirects.
I just destroyed my non-inkognito chrome because of a one character typo caused production settings to be used instead of local settings, causing a permanent redirect from http://localhost:8000/ to https://localhost:8000/ 

Okay, clearing cache as #9 sais, actually works, but that is really well hidden (It took me some time finding the correct button even with that explaination).
So if you ever mess up a permanent redirect on a live server; you'll never be able to explain to a customer how to do this, ignoring that you cannot possibly guide every visitor to do so... So it should be a way to clear this cache from server side somehow.

clearing the 301 cache by using chrome://net-internals is very un-intuitive, it should be cleared by "Disable Cache" function in the debug inspector, or in by clicking "clear site data" button in Application tab of the inspector, neither of them currently works as of version 62

tbf,  it should be cleared by the "empty cache and hard reload" command under the refresh button, which is now only visible when the inspector window is open.  

For development purposes, there should be a way to turn off redirect caching altogether.

It appears that Chrome 68 does clear the redirect cache if you click "Disable Cache" under the Network tab in Developer Tools and then reload. Don’t know if this cache clearing was introduced recently or has always been there.

For the localhost case, I would check what it says for the 301 entry in the Network tab. Does it say "from disk cache"? In that case, it’s cached, otherwise it’s not.

FWIW, I think Shift-Refresh should clear the redirect cache for the requested URL. This would be helpful for end-users in case the webmaster set the redirect incorrectly for whatever reason and then fixed the error. Refresh alone doesn’t need to do this, only Shift-Refresh.