Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Curl error 55 Broken pipe, errno 32
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Arun Jaganath via curl-library <curl-library_at_lists.haxx.se>
Date: Wed, 21 Dec 2022 13:18:10 +0530
Hi Jakub
Thanks for the inputs.... I did try the same command and same file from the
windows PC and same version of curl.... The file upload was returned as
successful. Kindly find the windows output attached....
On Wed, Dec 21, 2022, 12:19 Arun Jaganath <arunjaganath_at_gmail.com> wrote:
> Does this mean that libcurl is expecting the server to read the data
> completely once it sees 100 continue from the server?
>
> On Wed, Dec 21, 2022, 11:51 Zakrzewski, Jakub via curl-library <
> curl-library_at_lists.haxx.se> wrote:
>
>> > I have a scenario where in when a file is uploaded to the server, if
>> the file fully exists on the server with matching etag, the server
>> responds back with a 200 and closes the connection without actually reading
>> the data being uploaded. But unfortunately on libcurl this response is
>> ignored and the broken pipe error is reported.... Is this a bug or is this
>> working as expected, if so how do I handle such cases.... Any help is
>> highly appreciated. Kindly find the curl verbose output attached...
>>
>> From my POV the server behaves weirdly - first it responds "100 Continue"
>> and then basically just rudely interrupts the client and closes the
>> connection. It should respond 2XX right away.
>> --
>> Unsubscribe: https://lists.haxx.se/listinfo/curl-library
>> Etiquette: https://curl.se/mail/etiquette.html
>>
>
Received on 2022-12-21
Date: Wed, 21 Dec 2022 13:18:10 +0530
Hi Jakub
Thanks for the inputs.... I did try the same command and same file from the
windows PC and same version of curl.... The file upload was returned as
successful. Kindly find the windows output attached....
On Wed, Dec 21, 2022, 12:19 Arun Jaganath <arunjaganath_at_gmail.com> wrote:
> Does this mean that libcurl is expecting the server to read the data
> completely once it sees 100 continue from the server?
>
> On Wed, Dec 21, 2022, 11:51 Zakrzewski, Jakub via curl-library <
> curl-library_at_lists.haxx.se> wrote:
>
>> > I have a scenario where in when a file is uploaded to the server, if
>> the file fully exists on the server with matching etag, the server
>> responds back with a 200 and closes the connection without actually reading
>> the data being uploaded. But unfortunately on libcurl this response is
>> ignored and the broken pipe error is reported.... Is this a bug or is this
>> working as expected, if so how do I handle such cases.... Any help is
>> highly appreciated. Kindly find the curl verbose output attached...
>>
>> From my POV the server behaves weirdly - first it responds "100 Continue"
>> and then basically just rudely interrupts the client and closes the
>> connection. It should respond 2XX right away.
>> --
>> Unsubscribe: https://lists.haxx.se/listinfo/curl-library
>> Etiquette: https://curl.se/mail/etiquette.html
>>
>
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
- text/plain attachment: Windowscurlresponse.txt