A server can respond different to both methods, or can block one of the two.
Signed-off-by: Boris Schrijver
Reviewed-by: John Snow
---
V2: Impovements over V1:
- Don't check for CURLE_WRITE_ERROR, on success CURLE_OK will be returned.
- Use
Dear all,
Thanks for your time so-far.
I send a mail to the libcurl development list and got a helpful reaction [1]! I
changed my patch accordingly. We now don't have to check for a CURLE_WRITE_ERROR
anymore and curl_easy_perform() will return CURLE_OK (0) on success.
Please review!
commit