[wp-trac] [WordPress Trac] #16889: Having a location header does not mean that there should be a redirection.

[WordPress Trac]

#16889: Having a location header does not mean that there should be a redirection.
-----------------------------+------------------------------
 Reporter:  hakre            |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  HTTP             |     Version:  3.1
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |
-----------------------------+------------------------------
Changes (by dd32):

 * keywords:  has-patch => has-patch close


Comment:

 Unfortunately, I don't think it's going to be possible to adhere to this
 specification.

 cURL(CURLOPT_FOLLOWLOCATION), HTTP Extension, and Streams (therefor PHP
 Internally) all follow redirects on 200 (ie. non-3xx) responses, this
 seems to be done (From what I can understand) for compatibility reasons
 with older web servers (unsure of which ones specifically)

 It's probably best to standardise on following location regardless of the
 response code as we're currently doing.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/16889#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software