Mercurial > hg > nginx
view src/misc/ngx_cpp_test_module.cpp @ 8057:ae2d62bb12c0
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.
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Fri, 15 Jul 2022 07:01:44 +0300 |
parents | f1e6f65ddfeb |
children |
line wrap: on
line source
// stub module to test header files' C++ compatibility extern "C" { #include <ngx_config.h> #include <ngx_core.h> #include <ngx_event.h> #include <ngx_event_connect.h> #include <ngx_event_pipe.h> #include <ngx_http.h> #include <ngx_mail.h> #include <ngx_mail_pop3_module.h> #include <ngx_mail_imap_module.h> #include <ngx_mail_smtp_module.h> #include <ngx_stream.h> } // nginx header files should go before other, because they define 64-bit off_t // #include <string> void ngx_cpp_test_handler(void *data); void ngx_cpp_test_handler(void *data) { return; }