Bugs item #2814005, was opened at 2009-06-29 16:17
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2814005&group_id=976
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: http
Group: wrong behaviour
>Status: Pending
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Marek DÄ…bek (lican)
Assigned to: Daniel Stenberg (bagder)
Summary: HTTP Proxy with Windows SSPI
Initial Comment:
When using libcurl with proxy authentication everything works as expected. The only problem is that the native windows mechanisms allow the username and password set to NULL (the currently logged in user credentials are used). Libcurl doesn't allow that to happen and with that some of the functionality available for Windows users is missing. The only problem is the line 4257 in url.c:
conn->bits.proxy_user_passwd =
(bool)(NULL != data->set.str[STRING_PROXYUSERNAME]);
In my opinion it should be changed to:
conn->bits.proxy_user_passwd =
#ifdef USE_WINDOWS_SSPI
conn->bits.proxy;
#else
(bool)(NULL != data->set.str[STRING_PROXYUSERNAME]);
#endif
This allows the user to pass NULL pointers for the username and password thus allowing to authenticate with native Windows mechanisms.
----------------------------------------------------------------------
Comment By: Daniel Stenberg (bagder)
Date: 2009-07-05 00:38
Message:
Thanks for reporting this issue and helping us improve curl and libcurl.
We're awaiting feedback in this issue. Due to this, I have set the state
of this issue to pending and it will automatically get closed later on
unless we get further info.
Please consider answering the outstanding questions or providing the
missing info so that we can proceed to resolve this issue!
----------------------------------------------------------------------
Comment By: Daniel Stenberg (bagder)
Date: 2009-06-30 23:18
Message:
As I mentioned on the mailing list, I don't think this is a good way to fix
the problem. And I think we can continue discussing this on the list.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2814005&group_id=976
Received on 2009-07-05