aboutsummaryrefslogtreecommitdiff
path: root/src/os/unix
diff options
context:
space:
mode:
authorMaxim Dounin <mdounin@mdounin.ru>2022-07-15 07:01:44 +0300
committerMaxim Dounin <mdounin@mdounin.ru>2022-07-15 07:01:44 +0300
commitf35475c083d4cfe56647b66387b60c55e25c27d0 (patch)
tree1bc937d3dec0c4575549292d82450cb69ca83d83 /src/os/unix
parent14341ce2377d38a268261e0fec65b6915ae6e95e (diff)
downloadnginx-f35475c083d4cfe56647b66387b60c55e25c27d0.tar.gz
nginx-f35475c083d4cfe56647b66387b60c55e25c27d0.zip
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.
Diffstat (limited to 'src/os/unix')
0 files changed, 0 insertions, 0 deletions