I usually want upload form named pipe, when transloading files from one filehost to another and I have only few disk space on my VPS to download files fully at first and then upload them.
However I often get "curl: (55) Send failure / broken pipe" error message when uploading from named pipe.
The pipe is fed by ffmpeg, but I got same experiences when the pipe is fed by bsdtar. I upload to depositfiles.com .
Error message always appears at position when 40 MB of data has been uploaded. I also tried to pass a http header field - H "Transfer-Encoding: Chunked" and ordinary pipe instead of named one but no success, I experienced a broken pipe error always at ~40 MB of data.
curl's formpost logic doesn't support reading from a pipe but must be able to get the size before the transfer starts, afair. I could very well be fixed to support "Transfer-Encoding: Chunked" (if the server isn't HTTP1.0) but it isn't right now. Patches very welcome. Right now, this issue should be fixed by properly documenting this limitation.
Konstantinusz commentedJul 30, 2015
I usually want upload form named pipe, when transloading files from one filehost to another and I have only few disk space on my VPS to download files fully at first and then upload them.
However I often get "curl: (55) Send failure / broken pipe" error message when uploading from named pipe.
The pipe is fed by ffmpeg, but I got same experiences when the pipe is fed by bsdtar. I upload to depositfiles.com .
Error message always appears at position when 40 MB of data has been uploaded. I also tried to pass a http header field - H "Transfer-Encoding: Chunked" and ordinary pipe instead of named one but no success, I experienced a broken pipe error always at ~40 MB of data.
On the producer side of the pipe:
On the consumer side:
What can I do to avoid such annoyances, and make the pipe / uploading intact?
The text was updated successfully, but these errors were encountered: