[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:  closed
 Priority:  normal     |   Milestone:
Component:  HTTP       |     Version:  3.1
 Severity:  normal     |  Resolution:  invalid
 Keywords:  has-patch  |
-----------------------+----------------------

Comment (by hakre):

 Replying to [comment:4 dd32]:
 > 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)

 Most certainly by [http://tools.ietf.org/html/rfc2616#section-6.2 6.2
 Response Header Fields] and
 [http://tools.ietf.org/html/rfc2616#section-14.30 14.30 Location].

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

 I now think so as well now. Thanks for your support so far.

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