515 An overview of 301, 302 and 307 The RFC 7231, the current reference for semantics and content of the HTTP/1.1 protocol, defines the 301 (Moved Permanently) and 302 (Found) status code, that allows the request method to be changed from POST to GET. 301 is a permanent redirect, and 302 is a temporary redirect. The browser is allowed to cache the 301 but 302 means it has to hit our system every time.
assuming that we want to minimize the load on our system, 301 is the right decision. On second thought, I didn't really answer the real question, "How long do browsers cache a 301," and my answer wouldn't help anybody who redirected a public-facing site where you probably need some way to permanently undo a 301 without knowing how many browsers in the wild have cached the redirect -- other answers partially address that scenario. I have over 50 html pages that I'm going to move to different folders in the same domain. How to properly make 301 redirects for each one?
301 building, Some people said to place the redirect in meta html tags... I thought maybe you had been scammed by someone. 301 is a huge area code, covering a portion of Maryland. I doubt all numbers from there are scams, but thanks for the warning. How can one easily test HTTP return codes, like, say, a 301 redirect?
301 building, For example, if I want to "see what's going on", I can use telnet to do something like this: ... $ telnet nytimes.com 80 Tr... It seems that 302 was originally intended to be a temporary redirect, (like 307), but in practice, most browsers treated it like a 303. But what's the difference between a 303 and a 301? Is 301 supposed to mean the redirect is more permanent? Learn how to resolve 301 redirection errors with step-by-step guidance from the Google Search Central Community.
