From 74816fed6c82132b0ef32bd8775b0ef659a5b4c3 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sun, 3 Apr 2005 22:46:25 +0000 Subject: Hardeep Singh reported a problem doing HTTP POST with Digest. (It was actually also affecting NTLM and Negotiate.) It turned out that if the server responded with 100 Continue before the initial 401 response, libcurl didn't take care of the response properly. Test case 245 and 246 added to verify this. --- lib/http.c | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'lib') diff --git a/lib/http.c b/lib/http.c index 308f9efc3..c689b6596 100644 --- a/lib/http.c +++ b/lib/http.c @@ -304,6 +304,10 @@ CURLcode Curl_http_auth_act(struct connectdata *conn) bool pickproxy = FALSE; CURLcode code = CURLE_OK; + if(100 == conn->keep.httpcode) + /* this is a transient response code, ignore */ + return CURLE_OK; + if(data->state.authproblem) return data->set.http_fail_on_error?CURLE_HTTP_RETURNED_ERROR:CURLE_OK; -- cgit v1.2.3