mirror of
https://github.com/curl/curl.git
synced 2026-08-26 00:13:34 +03:00
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.
This commit is contained in:
parent
b4c9789d5f
commit
74816fed6c
4 changed files with 98 additions and 1 deletions
|
|
@ -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;
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue