Viewing all changes in revision 7062.
- Committer: Maxim Dounin
- Date: 2022-07-15 04:01:44 UTC
- Revision ID: git-v1:f35475c083d4cfe56647b66387b60c55e25c27d0
Range filter: clearing of pre-existing Content-Range headers.
Some servers might emit Content-Range header on 200 responses, and this
does not seem to contradict RFC 9110: as per RFC 9110, the Content-Range
header has no meaning for status codes other than 206 and 416. Previously
this resulted in duplicate Content-Range headers in nginx responses handled
by the range filter. Fix is to clear pre-existing headers.
Some servers might emit Content-Range header on 200 responses, and this
does not seem to contradict RFC 9110: as per RFC 9110, the Content-Range
header has no meaning for status codes other than 206 and 416. Previously
this resulted in duplicate Content-Range headers in nginx responses handled
by the range filter. Fix is to clear pre-existing headers.
- files modified:
- src/http/modules/ngx_http_range_filter_module.c
expand all
collapse all
added
removed
