Gzip static: ranges support (ticket #2349).
In contrast to on-the-fly gzipping with gzip filter, static gzipped representation as returned by gzip_static is persistent, and therefore the same binary representation is available for future requests, making it possible to use range requests. Further, if a gzipped representation is re-generated with different compression settings, it is expected to result in different ETag and different size reported in the Content-Range header, making it possible to safely use range requests anyway. As such, ranges are now allowed for files returned by gzip_static.
This commit is contained in:
parent
0940a055c9
commit
2a56f86948
|
@ -247,6 +247,8 @@ ngx_http_gzip_static_handler(ngx_http_request_t *r)
|
|||
ngx_str_set(&h->value, "gzip");
|
||||
r->headers_out.content_encoding = h;
|
||||
|
||||
r->allow_ranges = 1;
|
||||
|
||||
/* we need to allocate all before the header would be sent */
|
||||
|
||||
b = ngx_calloc_buf(r->pool);
|
||||
|
|
Loading…
Reference in New Issue