Opened 2 months ago
Last modified 2 months ago
#11160 new enhancement
"-http_proxy" authentication support
| Reported by: | ffmpeg_bug_reporter | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | avformat |
| Version: | 6.1.1 | Keywords: | http_proxy |
| Cc: | MasterQuestionable | Blocked By: | |
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
Summary of the bug:
The current version of ffmpeg cannot use an HTTP proxy that requires username and password authentication.
After examining the source code, the reason is that the auth_type of the proxy cannot be assigned by default.
(libavformat/http.c:2137 s->proxy_auth_state)
I think a parameter should be added, such as proxy_auth_type.
How to reproduce:
% ffmpeg -loglevel debug -http_proxy http://user:pwd@127.0.0.1:1234 -i "https://abc.abc" output.mp4 ffmpeg version v6.1.1 built on Apple clang
Change History (4)
comment:1 by , 2 months ago
| Cc: | added |
|---|---|
| Summary: | The http_proxy requiring authentication does not work → "-http_proxy" authentication support |
| Type: | defect → enhancement |
comment:2 by , 2 months ago
comment:3 by , 2 months ago
There are two (or more?) authentication types.
It is impossible to determine which one to use through the URI?
comment:4 by , 2 months ago
͏ No idea...
͏ https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#authentication_schemes
͏ .
͏ Are they all request header based?
͏ See also: https://forum.vivaldi.net/topic/77666
Note:
See TracTickets
for help on using tickets.
͏ Maybe the proper fix is not new option:
͏ But improving the URI handling?