Yes, I suspected as much - thanks for the confirmation. More digging
required

On 30 April 2018 at 13:15, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Tue, 24 Apr 2018, Neil Canham wrote:
>
> Re-reading my post I realise it wasn't clear enough. It is the socket
>> that I'm writing the data to in my client application that we obtain from
>> Curl. It is also this same socket that is the source of the FIN that we
>> detect arriving at the proxy. The next time we try to write to the socket
>> on the client to send the next buffer of data, it can't be written to -
>> closed. When I have the same client application with a socket that I didn't
>> get from Curl this doesn't happen - we write and write until we are done
>> then we close the socket.
>>
>
> Still, libcurl doesn't make any magic sockets. It creates sockets just
> like anyone else and when you ask for it, it hands it over to the
> application. If that then doesn't work, it's not clear to me what curl can
> do about that!
>
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html
>

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-04-30