[FFmpeg-trac] #8642(undetermined:new): HTTP 302 redirect to udp://
FFmpeg
trac at avcodec.org
Wed Apr 29 22:31:43 EEST 2020
#8642: HTTP 302 redirect to udp://
-------------------------------------+-------------------------------------
Reporter: barhom | Owner:
Type: defect | Status: new
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: http | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by barhom):
Replying to [comment:1 cehoyos]:
> If you want to report a bug, please test current FFmpeg git head and
provide the command line you tested together with the complete, uncut
console output.
I guess this is more of a question to see if it is a bug or not first.
I am using the latest git.
Replying to [comment:2 Tjoppen]:
> What do you expect this to do? UDP is not an application protocol. Are
you trying to have it upgrade to QUIC? There's a specific mechanism for
that, but it's far from being standardized.
Short explanation:
I expect ffmpeg to start reading from UDP.
Long explanation:
This has nothing to do with QUIC. I am using a "load balancer" for my
input of sort that gives a 302 redirect. This load balancer may return a
http://, https:// or udp:// address.
I expect the following to happen;
If;
{{{
ffmpeg -i http://example.com/?ch=X
}}}
returns a 302 that looks like this;
{{{
location: udp://239.193.0.188:3301?pkt_size=1316
}}}
Then I expect ffmpeg to behave as if I had run,
{{{
ffmpeg -i udp://239.193.0.188:3301?pkt_size=1316
}}}
Do you see the use case?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8642#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list