Hello, bringing this back from the grave.
Nicolas Frattaroli:
> if I'll change it to anything then maybe max_requested_size, but
> max_range_size seems less clear to me because that it does this through
> the range header is not relevant to the user, its effect is, which is
> that FFmpeg requests
On 08.01.25 08:35, Marth64 wrote:
As it’s effectively controlling the value of the Range header, this is also
something one can do with curl’s -r switch or -headers on the http protocol
handler now. So I think it’s reasonable to make it available as an option.
I would not necessarily brand it as
As it’s effectively controlling the value of the Range header, this is also
something one can do with curl’s -r switch or -headers on the http protocol
handler now. So I think it’s reasonable to make it available as an option.
I would not necessarily brand it as a hack in the commit message since
t
On 02/01/2025 06:52, Nicolas Frattaroli wrote:
In some cases, webservers may return content more quickly if one
sends many small requests rather than one big request. Clients may
wish to opt-in to this workaround.
For this purpose, add a max_request_size AVOption, which returns
EOF if max_reques
> 在 2025年1月2日，上午5:52，Nicolas Frattaroli 写道：
>
> In some cases, webservers may return content more quickly if one
> sends many small requests rather than one big request. Clients may
> wish to opt-in to this workaround.
>
> For this purpose, add a max_request_size AVOption, which returns
> EOF
In some cases, webservers may return content more quickly if one
sends many small requests rather than one big request. Clients may
wish to opt-in to this workaround.
For this purpose, add a max_request_size AVOption, which returns
EOF if max_request_size is exceeded, causing a new request with
an
