Thanks Daniel.

You are correct, one type of requests has CURLOPT_HTTPROXYTUNNEL set and the other does not; yet they both go through the same proxy, hence the confusion.
Would you like me to file a bug on this?

- Jad

> Date: Tue, 3 Nov 2009 19:58:34 +0100
> From: daniel_at_haxx.se
> To: curl-library_at_cool.haxx.se
> Subject: Re: Avoding connection re-use when using CURLOPT_HTTPPROXYTUNNEL
>
> On Mon, 2 Nov 2009, Jad Chamcham wrote:
>
> > I have a question regarding how to avoid the re-use of HTTP connections when
> > using CURLOPT_HTTPPROXYTUNNEL.
>
> > Essentially if the app is going through a proxy and uses the CONNECT method
> > for certain requests, how can I avoid subsequent requests (that don't use
> > the CURLOPT_HTTPPROXYTUNNEL flag) from re-using the same connection, which
> > will make the proxy tunnel these requests through to the wrong destination.
>
> Ah, are you saying that the second connection is still using the proxy, just
> not with CURLOPT_HTTPPROXYTUNNEL set? If that is the case, it sounds like
> you've stepped right into a bug that needs to be fixed.
>
> > What would be the best way to address this.
>
> Make sure that the proxytunnel option is also taken into account when a
> connection is re-used or not.
>
> > Please note that I am using the multi interface.
>
> The connection re-use logic is the exact same no matter which interface is
> used.
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html
                                               

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2009-11-04