search

GyanD / codexffmpeg

Support for https://www.gyan.dev/ffmpeg
1.43k stars 108 forks source link

option -user-agent not does not work #113

Closed diamond-info closed 8 months ago

diamond-info commented 8 months ago

I tried changing the -user-agentent option to insert my ID from the latest chrome browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 but I get an error in the form of text '-user-agent' ...Unrecognized option 'user-agent' if I use the option: -headers User-Agent: "Mozilla/...." then in my log I see that ffmpeg continues to use the default settings:

User-Agent: Lavf/60.16.100
Accept: */*
Range: bytes=0-
Connection: close
Host: flashvideo.rferl.org
Icy-MetaData: 1

Thus, this parameter has no effect. I found a similar problem here https://trac.ffmpeg.org/ticket/1291 and it says that it has been successfully solved in the new version. I was testing on the latest build of version 6.1.1 for Windows.

GyanD commented 8 months ago

The option name is -user_agent

diamond-info commented 8 months ago

Oh yes, I'm sorry, this parameter does not cause an error, but the log response shows that the built-in identifier is still being used:

Reading option '-user_agent' ... matched as AVOption 'user_agent' with argument ' Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36'.
.....
[tcp @ 0000000000575380] Successfully connected to 127.0.0.1 port 9095
[https @ 000000000056d480] request: GET /Videoroot/Pangeavideo/2024/01/0/01/01000000-0a00-0242-21dc-08dc184657ab_720p.mp4 HTTP/1.1
User-Agent: Lavf/60.16.100
Accept: */*
Range: bytes=0-
Connection: close
Host: flashvideo.rferl.org
Icy-MetaData: 1
GyanD commented 8 months ago

This is better handled at the ffmpeg bug tracker @ trac.ffmpeg.org