Hi, folks!
I’ve just kicked the ngx_openresty 1.0.6.12 release out of the door,
which
is the first stable release of ngx_openresty based on the nginx 1.0.6
core:
http://openresty.org/#Download
Here goes the complete change log, as compared to the last stable
release
1.0.5.1:
-
upgraded RdsJsonNginxModule to v0.12rc4.
- made rds_json_ret honor rds_json_success_property and
rds_json_user_property. thanks Liseen Wan (万珣新) - only register our output filters when the rds_json directive is
actually used in nginx.conf.
- made rds_json_ret honor rds_json_success_property and
-
upgraded RdsCsvNginxModule to v0.03.
- only register our output filters when the rds_csv directive is
actually used in nginx.conf.
- only register our output filters when the rds_csv directive is
-
added new options --with-luajit=PATH and --with-lua51=PATH to the
./configure script. thanks NginxUser. -
upgraded DrizzleNginxModule to v0.1.1.
-
upgraded RdsJsonNginxModule to 0.12rc3.
- implemented new directive rds_json_root.
- implemented new directive rds_json_success_property.
- implemented new directive rds_json_user_property.
-
upgraded LuaNginxModule to 0.3.1rc3.
- implemented and documented the API for reading response headers
from
within Lua: value = ngx.header.HEADER. - fixed a bug when setting a multi-value response header to a
single
value (via writing to ngx.header.HEADER): the single value will be
repeated on each old value.
- implemented and documented the API for reading response headers
-
upgraded EchoNginxModule to 0.37rc4.
- fixed a bug in echo_after_body: when network is not perfect,
data
truncation might occur. we should have taken into account
NGX_AGAINreturned by the downstream output filters. thanks Sparsh
Gupta.
- fixed a bug in echo_after_body: when network is not perfect,
-
upgraded HeadersMoreNginxModule to v0.16rc2.
- fixed a bug when setting a multi-value response header to a
single
value: the single value will be repeated on each old value.
- fixed a bug when setting a multi-value response header to a
-
applied the patch from Maxim D. to fix a bug in the standard
ngx_gzip module when dealing with empty flush buffers:
[PATCH 11 of 31] Gzip filter: handle empty flush buffers -
updated the no-pool-patch to eliminate the -Wset-but-not-used
warnings
issued by gcc 4.6.0. -
upgraded LuaNginxModule to 0.3.1rc1.
- fixed a bug when the both the main request and the subrequest
are
POST requests with a body: we should not forward the main
request’s
Content-Length headers to the user subrequests. thanks 朱峰.
- fixed a bug when the both the main request and the subrequest
-
upgraded HeadersMoreNginxModule to 0.16rc1.
- fixed on-demand hander/filter registration trick for HUP signal
restarts. - added some debugging outputs that can be enabled by the
–with-debugoption when building Nginx or
OpenResty.
- fixed on-demand hander/filter registration trick for HUP signal
-
Upgraded the nginx core to 1.0.6.
Enjoy!
-agentzh