From: Steve Holme Date: Sun, 14 Dec 2014 12:07:57 +0000 (+0000) Subject: ntlm: Fixed return code for bad type-2 Target Info X-Git-Tag: curl-7_40_0~155 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=52a4d6b8aee78f748924ed9f5217e4287df4593f;p=thirdparty%2Fcurl.git ntlm: Fixed return code for bad type-2 Target Info Use CURLE_BAD_CONTENT_ENCODING for bad type-2 Target Info security buffers just like we do for bad decodes. --- diff --git a/lib/curl_ntlm_msgs.c b/lib/curl_ntlm_msgs.c index d99a70f49b..ece1d0fa45 100644 --- a/lib/curl_ntlm_msgs.c +++ b/lib/curl_ntlm_msgs.c @@ -201,7 +201,7 @@ static CURLcode ntlm_decode_type2_target(struct SessionHandle *data, (target_info_offset < 48)) { infof(data, "NTLM handshake failure (bad type-2 message). " "Target Info Offset Len is set incorrect by the peer\n"); - return CURLE_REMOTE_ACCESS_DENIED; + return CURLE_BAD_CONTENT_ENCODING; } ntlm->target_info = malloc(target_info_len);