[wp-trac] Re: [WordPress Trac] #4790: Tracback should 301 redirect instead of 302

[WordPress Trac]

#4790: Tracback should 301 redirect instead of 302
-------------------------+--------------------------------------------------
 Reporter:  joostdevalk  |        Owner:  anonymous 
     Type:  defect       |       Status:  reopened  
 Priority:  normal       |    Milestone:  2.4 (next)
Component:  XML-RPC      |      Version:  2.3       
 Severity:  minor        |   Resolution:            
 Keywords:  2nd-opinion  |  
-------------------------+--------------------------------------------------
Changes (by markjaquith):

  * milestone:  2.3 => 2.4 (next)

Comment:

 301 is not correct.  404 is not correct either.

 303 is a possibility.


 ----
 303 See Other

 The response to the request can be found under a different URI and SHOULD
 be retrieved using a GET method on that resource. This method exists
 primarily to allow the output of a POST-activated script to redirect the
 user agent to a selected resource. The new URI is not a substitute
 reference for the originally requested resource. The 303 response MUST NOT
 be cached, but the response to the second (redirected) request might be
 cacheable.

 The different URI SHOULD be given by the Location field in the response.
 ----

 No proxy issues here, as 303s shouldn't be cached.  And it doesn't imply
 that the redirected URL is a substitute for the original URL.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/4790#comment:6>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software