[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:  has-patch    |  
-------------------------+--------------------------------------------------
Comment (by markjaquith):

 301 is cacheable (for instance, by proxies).  If someone clicks a
 trackback URL link through a proxy and then someone through that same
 proxy tries to send a trackback, the 301 from before might be cached, and
 the Trackback might fail.  It also suggests that the new URL is a
 substitute reference for the requested URL.  It is not.

 307 is also incorrect because it suggests that the new URL is a substitute
 reference for the requested URL.

 302 has the same problem.

 405 is a really specific match, but doesn't allow us to do a redirect (PHP
 sends a 302 if you try), so that loses because of user-unfriendliness

 303 is the only one that allows the redirect but does not suggest that the
 redirected URL is a substitute for the original URL.

 But in any case, this is going to have to miss the 2.3 boat.  We can
 resume discussion once 2.3 is branched off next month.

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