[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):

 The 1xx errors will be being raised by cURL/http internally, we currently
 check to see if the error it has raised is a redirect and leave it at
 that.

 If 1xx errors are pretty much invalid final responses (Pretty sure they
 are, they expect a next response correct?) then perhaps we can standardise
 on returning an error for those cases.

 fsockopen is out on it's own there, so that WP_Error response set for 4xx
 should probably be canned.

 I've said it elsewhere that a WP_Error response from the API should be
 considered a failed request - either network based or a 404(or similar)
 being returned - based on fsockopen()'s responses.

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