#4039 closed defect (fixed)
HTTP error-responses don't result in error code being returned by top level code
Reported by: | quandt | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | avformat |
Version: | unspecified | Keywords: | http |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
When issuing calls like this:
#!/bin/bash
ffmpeg -i http://somehost/somecontent.type someout.mkv
result=$?
If the connection is lost or something wonky happens out on the server, while the code detects the error and stops processing, there is no error code propogated on exit, ie result in the above will always = 0 (no error).
Simple way to replicate this is to issue "service apache2 restart" on a server you have access to where you are pulling the source from.
Attachments (1)
Change History (5)
by , 10 years ago
Attachment: | ffmpeg-20141016-191035.log added |
---|
comment:1 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 10 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
there was a bug in http.c, ill post a fix to the ML in a moment
"-xerror 1" is still needed of course though
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
should be fixed in 3668701f96005f4f7fc3145c800911e39351c132
comment:4 by , 10 years ago
Keywords: | exit code removed |
---|
this requires "-xerror 1"
if thats not sufficient then its a bug in the specific demuxer which fails to return an error code
please open or reopen the ticket if xerror doesnt help, and provide information about the format that failed