[FFmpeg-user] FFmpeg: how to output over HTTP

Glenn W wolfe.t.glenn at gmail.com
Wed Mar 20 03:05:19 EET 2019

Thank you Moritz,

I did not know that I was running Wireshark on the wrong network interface
- that makes a lot more sense now.

Please see the new attached PCAP file with a sample of the correct
Wireshark output bound to localhost. (had to gzip this one since it was
pretty big) ;

I do see some VERY sporadic HTTP POST headers, I could only find 1 out of
over 6000 and it came at the very end (see Frame 6137 of the sample).
Further, it appears that Wireshark does not even recognize this POST as
HTTP protocol. I am wondering if this is the expected behavior? It seems
very strange to me.

BTW I could actually share a small sample of the actual output since it was
so big (ffmpeg user mail list would not allow) - but there were 5000+
packets before that looked similar with zero HTTP headers whatsoever.

Since my video server (receiver) sits behind an HTTP load balancer, it will
need to see an HTTP route in order receive the packets from the FFmpeg
client (sender).

If I can get an HTTP route through to the receiver, I am thinking I could
use the below to maintain a persisted connection so that rest of data
packets can just be sent over TCP:

*Use persistent connections if set to 1, default is 0.*

Please advise. Really appreciate your help with debugging this issue.

Glenn W

On Tue, Mar 19, 2019 at 7:33 PM Moritz Barsnick <barsnick at gmx.net> wrote:

> On Tue, Mar 19, 2019 at 22:49:32 +0100, Carl Eugen Hoyos wrote:
> > 2019-03-19 18:46 GMT+01:00, Glenn W <wolfe.t.glenn at gmail.com>:
> >
> > > Please see the below full console output
> >
> > Unfortunately not;-(
> Too bad it'ss in an external link (which tends to disappear after
> weeks).
> > Anyway, this was certainly transmitted via http.
> According to the ffmpeg logs - yes, obviously.
> According to the PCAP: hmm.
> Well, the command lines show port 5558:
> > chill at life ~$ ffmpeg -listen 1 -i http://localhost:5558/video -f null -
> but I don't see a single packet related to port 5558 in that PCAP file.
> (Filter: tcp.port == 5888). I wonder what was captured - probably eth0
> (or whatever the physical interface is called) and not lo (to which
> localhost is bound). No wonder you, Glenn, don't see HTTP traffic if
> you don't actually capture the ffmpeg traffic...
> Moritz
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ffmpeg-abridged-packet-sampling.pcapng.gz
Type: application/x-gzip
Size: 585834 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-user/attachments/20190319/d04cc492/attachment.bin>

More information about the ffmpeg-user mailing list