> 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
