Support for gzip compression under HTTP using the zlib library.
Problems
This issue may require the proper definition of middleware layers, at least a pluggable point in the write_connection method. So that a code portion may re-encode the data as gzip.
A major issue is the calculus of the size of the message (Content-Length) to be sent in advance for the header definition. This may require the complete set of information to be available before the message is sent.
Discovery
Need to check on nginx runtime to verify if the Content-Length is sent for gzip scenarios or if chunk encoding is used as an alternative.
Note that the Content-Length header is not set when using either version. Keepalives will therefore be impossible with version 1.0, while for 1.1 it is handled by chunked transfers. from here
Example
http://www.zlib.net/zlib_how.html
Reference
Nginx HttpGzipModule
ngx_http_gzip_filter_module.c
Support for gzip compression under HTTP using the zlib library.
Problems
This issue may require the proper definition of middleware layers, at least a pluggable point in the write_connection method. So that a code portion may re-encode the data as gzip.
A major issue is the calculus of the size of the message (Content-Length) to be sent in advance for the header definition. This may require the complete set of information to be available before the message is sent.
Discovery
Need to check on nginx runtime to verify if the Content-Length is sent for gzip scenarios or if chunk encoding is used as an alternative.
Note that the Content-Length header is not set when using either version. Keepalives will therefore be impossible with version 1.0, while for 1.1 it is handled by chunked transfers. from here
Example
http://www.zlib.net/zlib_how.html
Reference
Nginx HttpGzipModule
ngx_http_gzip_filter_module.c