]> git.kaiwu.me - nginx.git/commit
projects / nginx.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 14341ce) | patch
Range filter: clearing of pre-existing Content-Range headers.
authorMaxim Dounin <mdounin@mdounin.ru>
Fri, 15 Jul 2022 04:01:44 +0000 (07:01 +0300)
committerMaxim Dounin <mdounin@mdounin.ru>
Fri, 15 Jul 2022 04:01:44 +0000 (07:01 +0300)
commitf35475c083d4cfe56647b66387b60c55e25c27d0
tree1bc937d3dec0c4575549292d82450cb69ca83d83tree | snapshot
parent14341ce2377d38a268261e0fec65b6915ae6e95ecommit | diff
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.
src/http/modules/ngx_http_range_filter_module.c diff | blob | history
nginx upstream