You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The HTTP spec dictates that a server may completely ignore the RANGE header if it doesn't support it.
It would be great if a little check was done to make sure the content-length of the response matches the request so we don't end up downloading entire databases.
Specifically I found that Cloudflare usually support partial ranges for cached files, but suddenly stops supporting them above a certain size limit. This left me scratching my head when I saw the seemingly stalled requests. Was only after checking my network activity that I saw it was downloading 700MB of data.
The text was updated successfully, but these errors were encountered:
The HTTP spec dictates that a server may completely ignore the RANGE header if it doesn't support it.
It would be great if a little check was done to make sure the content-length of the response matches the request so we don't end up downloading entire databases.
Specifically I found that Cloudflare usually support partial ranges for cached files, but suddenly stops supporting them above a certain size limit. This left me scratching my head when I saw the seemingly stalled requests. Was only after checking my network activity that I saw it was downloading 700MB of data.
The text was updated successfully, but these errors were encountered: