[wp-trac] Re: [WordPress Trac] #4790: Tracback should 301 redirect
instead of 302
WordPress Trac
wp-trac at lists.automattic.com
Wed Aug 29 14:26:29 GMT 2007
#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 Otto42):
303 is the correct way to do this, I say commit it.
For reference, the 300 codes work like this (under HTTP 1.1) :
* 300 Multiple Choices (like if you offer different languages.. not used
much)
* 301 Moved Permanently (obvious)
* 302 Found (temporary redirect - deprecated in favor of 303 and 307)
* 303 See Other (redirection to be used after a successful POST, user
agent should do a GET on the redirected URL)
* 304 Not Modified (user agent did a conditional GET but the document was
not changed since the time given)
* 305 Use Proxy (the URL must be accessed through a proxy, the Location:
gives the proxy that must be used)
* 306 Unused
* 307 Temporary Redirect (a real temporary redirection, a user agent
doing a POST should do a repost to the new URL.. often causes the browser
to ask the user for confirmation to do that)
--
Ticket URL: <http://trac.wordpress.org/ticket/4790#comment:9>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list