Skip to content

Commit

Permalink
http_ntlm: Use the SASL functions instead
Browse files Browse the repository at this point in the history
In preparation for moving the NTLM message code into the SASL module
use the SASL functions in the HTTP code instead.
  • Loading branch information
captain-caveman2k committed Nov 9, 2014
1 parent 9dbbba9 commit 48d19ac
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions lib/curl_ntlm.c
Expand Up @@ -85,7 +85,7 @@ CURLcode Curl_input_ntlm(struct connectdata *conn,
header++;

if(*header) {
result = Curl_ntlm_decode_type2_message(conn->data, header, ntlm);
result = Curl_sasl_decode_ntlm_type2_message(conn->data, header, ntlm);
if(result)
return result;

Expand Down Expand Up @@ -175,8 +175,8 @@ CURLcode Curl_output_ntlm(struct connectdata *conn, bool proxy)
case NTLMSTATE_TYPE1:
default: /* for the weird cases we (re)start here */
/* Create a type-1 message */
result = Curl_ntlm_create_type1_message(userp, passwdp, ntlm, &base64,
&len);
result = Curl_sasl_create_ntlm_type1_message(userp, passwdp, ntlm, &base64,
&len);
if(result)
return result;

Expand All @@ -195,8 +195,8 @@ CURLcode Curl_output_ntlm(struct connectdata *conn, bool proxy)

case NTLMSTATE_TYPE2:
/* We already received the type-2 message, create a type-3 message */
result = Curl_ntlm_create_type3_message(conn->data, userp, passwdp,
ntlm, &base64, &len);
result = Curl_sasl_create_ntlm_type3_message(conn->data, userp, passwdp,
ntlm, &base64, &len);
if(result)
return result;

Expand Down

0 comments on commit 48d19ac

Please sign in to comment.