nginx: 1f3bf1734a77

changeset 7686:1f3bf1734a77

Xslt: disabled ranges. Previously, the document generated by the xslt filter was always fully sent to client even if a range was requested and response status was 206 with appropriate Content-Range. The xslt module is unable to serve a range because of suspending the header filter chain. By the moment full response xml is buffered by the xslt filter, range header filter is not called yet, but the range body filter has already been called and did nothing. The fix is to disable ranges by resetting the r->allow_ranges flag much like the image filter that employs a similar technique.

author Roman Arutyunyan <arut@nginx.com>

date Wed, 22 Jul 2020 22:16:19 +0300

parents 4f30f75dbdf3

children d752a2c76d49

files src/http/modules/ngx_http_xslt_filter_module.c

diffstat

1 files changed, 1 insertions(+), 0 deletions(-) [+]

line wrap: on

line diff

--- a/src/http/modules/ngx_http_xslt_filter_module.c	Tue Jul 21 20:34:29 2020 +0300
+++ b/src/http/modules/ngx_http_xslt_filter_module.c	Wed Jul 22 22:16:19 2020 +0300
@@ -233,6 +233,7 @@
     ngx_http_set_ctx(r, ctx, ngx_http_xslt_filter_module);
 
     r->main_filter_need_in_memory = 1;
+    r->allow_ranges = 0;
 
     return NGX_OK;
 }