On Mon, 14 Mar 2011, Jorge Velázquez wrote:

> Olivier is correct, this is what I am seeing, also. In order to view the
> final status code, I had to implement a header function and manually parse
> out the 2nd response code when the request is completed. Since, per the
> spec, a final status code is required in all cases, as far as I can tell, it
> seems reasonable to make the 2nd response code the value returned from
> CURLINFO_RESPONSE_CODE in all cases.

I can only agree and I consider this a bug.

Feel free to dig in and see if you can fix it!

-- 
  / daniel.haxx.se

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-03-15