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.
This commit is contained in:
parent
7287c1c2f4
commit
88a0db101e
1 changed files with 1 additions and 0 deletions
|
@ -233,6 +233,7 @@ ngx_http_xslt_header_filter(ngx_http_request_t *r)
|
|||
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;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue