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
What is the problem your feature solves, or the need it fulfills?
When adjusting response headers, ResponseCompressionCtx will currently remove the Content-Length header as the old header does not apply. A potentially present Accept-Ranges: bytes header is left untouched however, even though ranged requests no longer make sense.
Describe the solution you'd like
Call resp.insert_header(&ACCEPT_RANGES, HeaderValue::from_static("none")) when compressing. This will both overwrite any existing Accept-Ranges header and explicitly indicate to the client that ranged requests are unsupported.
What is the problem your feature solves, or the need it fulfills?
When adjusting response headers,
ResponseCompressionCtx
will currently remove theContent-Length
header as the old header does not apply. A potentially presentAccept-Ranges: bytes
header is left untouched however, even though ranged requests no longer make sense.Describe the solution you'd like
Call
resp.insert_header(&ACCEPT_RANGES, HeaderValue::from_static("none"))
when compressing. This will both overwrite any existingAccept-Ranges
header and explicitly indicate to the client that ranged requests are unsupported.Describe alternatives you've considered
N/A
Additional context
Accept-Ranges header spec
The text was updated successfully, but these errors were encountered: