Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I often get curl: (55) Send failure error message when uploading from named pipe #360

Konstantinusz opened this issue Jul 30, 2015 · 1 comment


Copy link

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 .
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:

mkfifo video.mkv
ffmpeg -i -map_chapters -1 video.mkv

On the consumer side:

curl -b cookie-file   -F "files=@video.mkv;filename=video.mkv" -F 'format=html5'  -F "member_passkey=XXXXXXXdv8yfw2w" -F 'fm=_root' -F 'fmh='  ""

What can I do to avoid such annoyances, and make the pipe / uploading intact?

@bagder bagder self-assigned this Aug 1, 2015
Copy link

bagder commented Aug 1, 2015

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.

@bagder bagder added the HTTP label Aug 1, 2015
@bagder bagder closed this as completed in c092b0f Aug 1, 2015
jgsogo pushed a commit to jgsogo/curl that referenced this issue Oct 19, 2015
@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

No branches or pull requests

2 participants