hamstar/curl — pull request #3 by xsist10 (2013-11-21 08:44:35+00:00)
Title: Updated curl_response to handle multiple HTTP status codes in the response

I've altered the curl_response to only return the final HTTP response detected as per RFC spec:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

"A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent."

Example response:

"HTTP/1.1 100 Continue

HTTP/1.1 200 OK
Date: Tue, 19 Nov 2013 20:50:45 GMT
Server: Apache/2.2.14 (Ubuntu)
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 12
Content-Type: application/json

{example: 1}"