Patrick Monnerat via curl-library writes:
> On 4/26/2020 4:44 PM, Jean-Francois Dockes wrote:
> >> Thanks for the CURLOPT_CONNECT_ONLY pointer.
> >>
> >> Is there something to prevent me from using the resulting socket fd with
> >> CURLOPT_OPENSOCKETFUNCTION / CURLOPT_SOCKOPTFUNCTION ? I see t
On 4/26/2020 4:44 PM, Jean-Francois Dockes wrote:
Thanks for the CURLOPT_CONNECT_ONLY pointer.
Is there something to prevent me from using the resulting socket fd with
CURLOPT_OPENSOCKETFUNCTION / CURLOPT_SOCKOPTFUNCTION ? I see that
this is a
bit convoluted, but it gains me the use of the lib
On 4/26/2020 4:44 PM, Jean-Francois Dockes wrote:
Ray Satiro via curl-library writes:
> On 4/26/2020 10:40 AM, Jean-Francois Dockes via curl-library wrote:
> > My apologies if this is a frequent question, I could not find an answer.
> >
> > It would be convenient for me to retrieve the lo
Ray Satiro via curl-library writes:
> On 4/26/2020 10:40 AM, Jean-Francois Dockes via curl-library wrote:
> > My apologies if this is a frequent question, I could not find an answer.
> >
> > It would be convenient for me to retrieve the local address of the
> > connected socket used for an HTT
On 4/26/2020 10:40 AM, Jean-Francois Dockes via curl-library wrote:
My apologies if this is a frequent question, I could not find an answer.
It would be convenient for me to retrieve the local address of the
connected socket used for an HTTP GET before the HTTP transaction
begins.
The pseudo HT
