[wp-trac] [WordPress Trac] #17010: Inconsistent handling of HTTP response codes

[WordPress Trac]

#17010: Inconsistent handling of HTTP response codes
--------------------------+------------------------------
 Reporter:  sivel         |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  HTTP          |     Version:  3.1
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+------------------------------

Comment (by dd32):

 It looks like the 100 error is being translated to a empty response, in
 the wild this is caused by: http://the-stickman.com/web-development/php-
 and-curl-disabling-100-continue-header/

 The HTTP Extension is based internally on cURL which is why it has the
 same response pattern - I don't think the Extension offers enough of a API
 to catch this particular issue; I personally question the value the HTTP
 Extension brings given it's either a cURL wrapper or a fopen() wrapper
 depending on the configuration.

 100 responses shouldn't be delivered to the client IMO, They're a
 informational reply from the server that states the actual response is
 about to come through. I'm not too sure what would happen with a legit 101
 response (With the Upgrade header set to HTTP/1.1 on a HTTP/1.0 request)

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