11.07.2015 Views

Network Working Group R. Fielding Request for Comments: 2616 ...

Network Working Group R. Fielding Request for Comments: 2616 ...

Network Working Group R. Fielding Request for Comments: 2616 ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Fielding</strong>, et al. Standards Track [Page 61]RFC <strong>2616</strong> HTTP/1.1 June 1999the user agent, selection of the most appropriate choice MAY beper<strong>for</strong>med automatically. However, this specification does not defineany standard <strong>for</strong> such automatic selection.If the server has a preferred choice of representation, it SHOULDinclude the specific URI <strong>for</strong> that representation in the Locationfield; user agents MAY use the Location field value <strong>for</strong> automaticredirection. This response is cacheable unless indicated otherwise.10.3.2 301 Moved PermanentlyThe requested resource has been assigned a new permanent URI and anyfuture references to this resource SHOULD use one of the returnedURIs. Clients with link editing capabilities ought to automaticallyre-link references to the <strong>Request</strong>-URI to one or more of the newreferences returned by the server, where possible. This response iscacheable unless indicated otherwise.The new permanent URI SHOULD be given by the Location field in theresponse. Unless the request method was HEAD, the entity of theresponse SHOULD contain a short hypertext note with a hyperlink tothe new URI(s).If the 301 status code is received in response to a request otherthan GET or HEAD, the user agent MUST NOT automatically redirect therequest unless it can be confirmed by the user, since this mightchange the conditions under which the request was issued.Note: When automatically redirecting a POST request afterreceiving a 301 status code, some existing HTTP/1.0 user agentswill erroneously change it into a GET request.10.3.3 302 FoundThe requested resource resides temporarily under a different URI.Since the redirection might be altered on occasion, the client SHOULDcontinue to use the <strong>Request</strong>-URI <strong>for</strong> future requests. This responseis only cacheable if indicated by a Cache-Control or Expires headerfield.The temporary URI SHOULD be given by the Location field in theresponse. Unless the request method was HEAD, the entity of theresponse SHOULD contain a short hypertext note with a hyperlink tothe new URI(s).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!