In my specific case it happens all the time, to the point that I always work with my development browsers cache disabled: if I need to test stuff with a non-development browser, I'm often using the Incognito Mode, which flushes its cache everytime the browser is closed. The only downside of that is that, whenever you're testing or developing a web site (or a web server such as IIS or NGINX) and temporarily configure a HTTP 301 that you want to change later on, you could run into that redirect for a long period of time, thus being unable to access the previously-301 URL, page or resource. This is a perfectly fine behaviour, as it's explicitly allowed by the RFC 7231 Section-6.4.2, which says the following:Ī 301 response is cacheable by default i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of ). As you most likely known since you found this post, Google Chrome - just like most other browsers - implements the 301 redirect caching, meaning that it will often locally cache the HTTP 301 redirects for a given amount of time without asking the server another HTTP response for that same URL.
0 kommentar(er)
