2011/8/14 Daniel Stenberg wrote:

> I would say that if it is a HTTP NTLM authentication that fails,
> CURLE_REMOTE_ACCESS_DENIED seems suitable but if it is a SMTP login that
> fails, CURLE_LOGIN_DENIED seems more applicable.

Ok.

> Yes new codes are cheap, sure, but for applications it is often easier with
> less codes with minor differences. Especially it is easier to not have to
> add new codes to handle when they upgrade libcurl...

True.

> In this case I don't think the existing ones are so bad that we need a new
> code. The ones we already have seem to cover the cases good enough IMHO.
>
> Or am I missing something?

Given that the core of NTLM authentication is going to be protocol
agnostic It would be useful if a generic CURLE_AUTH_ERROR already
existed in order to allow it to bubble up from core NTLM functions all
the way up.

But I certainly can not justify the need for an additional code for
this at this moment.

-- 
-=[Yang]=-
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html