Daniel Stenberg wrote:
> On Mon, 11 Feb 2008, Jeremy Rottman wrote:
>
>> Every time I try to connect, I get a 401 error. I am using the same
>> connection method that I would use if I was using system curl.
>
> [...]
>
> So enable VERBOSE, or if the binding supports it use DEBUGFUNCTION to
> get more info about what libcurl does and doesn't etc.
>
> What libcurl version are you using?
>
This is the output I get from CURLOPT_VERBOSE.

* About to connect() to rets.armls.mlsrets.com port 80
* Trying 65.83.83.235... * connected
* Connected to rets.armls.mlsrets.com (65.83.83.235) port 80
* Server auth using Basic with user 'CRIL01'
> GET /rets/login HTTP/1.1
Authorization: Basic Q1JJTDAxOkpuITIzQA==
Host: rets.armls.mlsrets.com
Accept: */*

< HTTP/1.1 401 Unauthorized
HTTP/1.1 401 Unauthorized
< Content-Length: 1944
Content-Length: 1944
< Content-Type: text/html
Content-Type: text/html
< Server: Microsoft-IIS/6.0
Server: Microsoft-IIS/6.0
< X-Powered-By: ASP.NET
X-Powered-By: ASP.NET
< WWW-Authenticate: Digest
qop="auth",realm="rets_at_marketlinx.com",nonce="8a37c64e9500f1b4523141b768ae5a83",opaque="13021957456066"
WWW-Authenticate: Digest
qop="auth",realm="rets_at_marketlinx.com",nonce="8a37c64e9500f1b4523141b768ae5a83",opaque="13021957456066"
< Date: Wed, 13 Feb 2008 19:57:45 GMT
Date: Wed, 13 Feb 2008 19:57:45 GMT
< Connection: close
Connection: close

This however, does not make any sense. As I am using digest auth.

I am currently running
curl 7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b
zlib/1.2.3 libidn/0.6.5
Received on 2008-02-13