3xx Redirection | Heaton Research

3xx Redirection

    The client must take additional action to complete the request.

  • 300: Multiple Choices
  • 301: Moved Permanently
  • This and all future requests should be directed to another URL.
  • 302: Found
  • This is the most popular redirect code, but also an example of industrial practice contradicting the standard. HTTP/1.0 specification (RFC 1945) required the client to perform temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to disambiguate between the two behaviors. However, majority of Web applications and frameworks still use the 302 status code as if it were the 303.
  • 303: See Other (since HTTP/1.1)
  • The response to the request can be found under another URL using a GET method.
  • 304: Not Modified
  • 305: Use Proxy (since HTTP/1.1)
  • Many HTTP clients (such as Mozilla and Internet Explorer) don't correctly handle responses with this status code.
  • 306 is no longer used, but reserved. Was used for 'Switch Proxy'.
  • 307: Temporary Redirect (since HTTP/1.1)
  • In this occasion, the request should be repeated with another URL, but future requests can still be directed to the original URL. In contrast to 303, the original POST request must be repeated with another POST request.
Copyright 2005-2009 by Heaton Research, Inc.