Hi Allen...

Have you done any more work on this? Do you have a newer patch that I should
try out?

Thanks,

...Karl

>From: Allen Chan Subject: Re: Passing raw data through a proxy
>Date: Mon, 16 Jan 2006 09:51:44 +0900
>
>On 1/15/06, Karl M wrote:
> > Why would I want to specify the local port? Is there a use case for
>that?
>
>Hi Karl,
>
>I agree that we should only add the functions that we need as well,
>sorry for bringing that up. As for the local port, our current
>firewall setup is very strict and would only allow connections through
>ports that are allowed by policy.
>
>In such case, I found it necessary to bind the socket to a pre-defined
>port number in order for the connection to proceed.
>
>I am not sure if I am the only one who needs this function though, but
>I did happen to read a post asking for that same feature a while back.
>
>Included is the patch I made with unidiff using winmerge. Browsing the
>file casually, you might see lines that were removed and then
>immediately added, could this possibly be differences in the EOL?
>
>But in any case, I think that would not cause any problems, well I hope.
>
>I hope that you find the changes as useful as I did, as meager as they
>are. I would be very grateful for any suggestions and criticisms.
>
>The functions currently included and how i call them are:
>
>curl_easy_setopt(http_handle, CURLOPT_CONNECT_ONLY, 1);
>- connect only no transmission, works with easy, multi, and shared.
>
>curl_easy_getinfo(http_handle, CURLINFO_SOCKET, &s);
>- get the low-level socket handle of the curl handle
>
>curl_easy_getinfo(http_handle, CURLINFO_LOCAL_PORT, &port);
>- get the local port of the curl handle.
>
>Allen
>
> >
> > >From: Daniel Stenberg Subject: Re: Passing raw data through a proxy
> > >Date: Sun, 15 Jan 2006 12:18:11 +0100 (CET)
> > >
> > >On Sun, 15 Jan 2006, Allen Chan wrote:
> > >
> > >>A new function springs to mind, what if you could also specify the
>socket
> > >>that libcurl would use? We already have specify-the-local-port, might
>as
> > >>well specify the socket too. Multiple proxy tunnelling anyone? Sounds
>like
> > >>a bad hacker movie.
> > >
> > >For that to work, it would not only mean specify-the-socket, it would
>have
> > >to mean that the socket is already connected to the peer/proxy.
> > >
> > >But I'd rather see actual use cases when we add new features, since
>adding
> > >them on a "they might be good to have some day"-basis risk bloating and
> > >complicating the lib sources without any useful purpose.
> > >
> > >--
> > > Commercial curl and libcurl Technical Support:
>http://haxx.se/curl.html
> >
> >
> >
Received on 2006-02-02