id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
16888	WP HTTP Curl transport is only handling some but not all redirect status codes.	hakre		"That's violating the specs by namely processing 301 and 302 only:

   HTTP status codes are extensible. HTTP applications are not required
   to understand the meaning of all registered status codes, though such
   understanding is obviously desirable. However, applications MUST
   understand the class of any status code, as indicated by the first
   digit, and treat any unrecognized response as being equivalent to the
   x00 status code of that class, with the exception that an
   unrecognized response MUST NOT be cached.

from: [http://tools.ietf.org/html/rfc2616#section-6.1.1 6.1.1 Status Code and Reason Phrase]


   For 3xx responses, the location SHOULD indicate the
   server's preferred URI for automatic redirection to the resource. The
   field value consists of a single absolute URI.

from: [http://tools.ietf.org/html/rfc2616#section-14.30 14.30 Location]"	enhancement	closed	normal		HTTP	3.1	normal	wontfix	has-patch	WordPress@…