My guess is that we configure the curl to support the full range of http auth methods.
Some of them like Digest require a challenge and realm etc so it's probably asking without auth header because it cannot create one until it gets that data. In the case of Basic you can send the login and pass right away but it does not know in advance that it will be basic.
Here is a snippet from the libcurl api docs:
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Both these options allow you to set multiple types (by ORing them together), to make libcurl pick the most secure one out of the types the server/proxy claims to support. This method does however add a round-trip since libcurl must first ask the server what it supports:
curl_easy_setopt(easyhandle, CURLOPT_HTTPAUTH, CURLAUTH_DIGEST|CURLAUTH_BASIC);
-------------------------------------------------------------------------------------------------------------------------------------------------------------This web request goes to a server running IIS on Windows Server 2003.
From: Brian West [mailto:brian@freeswitch.org]
Sent: Monday, October 05, 2009 5:43 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] mod_xml_curl http POST is inconsistent/bug
Are you using something other than apache?
/b
On Oct 5, 2009, at 1:25 PM, Christian Damianidis wrote:
The inconsistent POST request sent by the module causes freeswitch to hang for 1-2 minutes during start-up.
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org