Yes, either that or libcurl should do the proxy authentication again after reuse, but I think the second option would complicate the logic in multi_runsingle a lot.

---
** [bugs:#1381] Problem with proxy CONNECT and Connection: Keep-Alive**
**Status:** open
**Created:** Wed Jun 11, 2014 02:07 PM UTC by Marcel Raad
**Last Updated:** Sun Jun 15, 2014 06:27 PM UTC
**Owner:** Daniel Stenberg
I'm using libcurl 7.37.0 (built with SSPI on Windows) and I'm trying to establish a proxy tunnel through a squid 3.2.11 proxy, which sends "Connection: Keep-Alive" with 407 responses. Both CURLOPT_HTTPPROXYTUNNEL and CURLOPT_CONNECT_ONLY are set to 1. When I use the easy API, everything works as expected, and also when I use a proxy that sends "(Proxy-)Connection: Close" with 407 responses, as the connection is not reused in this case.
But when I use the multi API and I don't submit valid proxy credentials for the first transfer, the connection gets reused for the second transfer (now with valid credentials). Because the first socket is then still valid in Curl_setup_conn, multi_runsingle switches immediately from CURLM_STATE_CONNECT to CURLM_STATE_DO, skipping proxy authentication, and then immediately to CURLM_STATE_DONE because of the connect_only option. libcurl then tells me that the connection was successful, but I cannot use the socket as the CONNECT still has not succeeded because of the missing proxy authentication.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.