Detailed HTTP Status Code 3

300 The requested resource has a range of optional feedback messages, each with its own specific address and browser-driven negotiation message. The user or browser can choose a preferred address for redirection. Unless this is a HEAD request, the response SHOULD include an entity with a list of resource properties and addresses from which the user or browser can choose the most appropriate redirection address. The format of this entity is determined by the format defined by Content-Type. The browser may automatically make the most appropriate choice based on the format of the response and the capabilities of the browser itself. Of course, the RFC 2616 specification does not specify how such automatic selection should be performed. If the server itself already has a preferred feedback option, the URI for this feedback should be specified in the Location; browsers may use the Location value as the address for automatic redirection. Also, unless otherwise specified, this response is also cacheable.

301 The requested resource has been permanently moved to a new location, and any future references to this resource SHOULD use one of the several URIs returned in this response. If possible, clients with link editing capabilities should automatically modify the requested address to the address returned from the server. Unless otherwise specified, this response is also cacheable. The new permanent URI shall be returned in the Location field of the response. Unless this is a HEAD request, the entity of the response SHOULD contain a hyperlink to the new URI and a short description. If this is not a GET or HEAD request, then the browser is prohibited from automatically redirecting unless confirmed by the user, as the conditions of the request may change accordingly. Note: For some browsers using the HTTP/1.0 protocol, when they send a POST request and get a 301 response, the subsequent redirect request will become a GET method.

302 The requested resource is now temporarily responding to the request from a different URI. Since such redirects are temporary, the client SHOULD continue to send future requests to the original address. This response is cacheable only if specified in Cache-Control or Expires. The new temporary URI SHOULD be returned in the Location field of the response. Unless this is a HEAD request, the entity of the response SHOULD contain a hyperlink to the new URI and a short description. If this is not a GET or HEAD request, the browser prohibits automatic redirection unless confirmed by the user, as the conditions of the request may change accordingly. Note: Although the RFC 1945 and RFC 2068 specifications do not allow the client to change the method of the request when redirecting, many existing browsers treat the 302 response as a 303 response and use GET to access the URI specified in the Location, ignoring The method originally requested. Status codes 303 and 307 were added to clarify what response the server expects from the client.

Transferred from Jiangsu Sanai Network"