# Ngx\_headers\_more module v0.16 released!

**URL:** <https://www.ruby-forum.com/t/ngx-headers-more-module-v0-16-released/215787>\
**Category:** NGINX\
**Created:** [January 16, 2012, 8:08am UTC](https://www.ruby-forum.com/t/ngx-headers-more-module-v0-16-released/215787 "2012-01-16T08:08:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [January 16, 2012, 8:08am UTC](https://www.ruby-forum.com/t/ngx-headers-more-module-v0-16-released/215787/1 "2012-01-16T08:08:25Z")

</div>

Hello, folks!

I’m happy to announce the v0.16 release of our ngx\_headers\_more module  
with various bug fixes accumulated in the last 6 months. You can  
download the source code tarball from the download page below:

[Tags · openresty/headers-more-nginx-module · GitHub](http://github.com/agentzh/headers-more-nginx-module/tags)

Special thanks go to all of our contributors and users!

Here’s the complete change log for this version (as compared to the  
last formal release, v0.15):

- bugfix: the on-demand handler/filter registration mechanism did not  
work fully for config reload via the HUP signal.

- bugfix: when setting a multi-value response header to a single  
value, the single value might be repeated on each old value.

- feature: added some debugging outputs that can be enabled by the  
–with-debug option when building nginx or ngx\_openresty.

- bugfix: we should set header hash using ngx\_hash\_key\_lc, not simply to

1. 

- bugfix: Setting Cache-Control response headers might not work with  
other nginx output filter modules because we did not properly prepare  
the r-\>cache\_control array at the same time.

- bugfix: more\_set\_input\_headers and more\_clear\_input\_headers did not  
handle the Accept-Encoding request headers properly. thanks ѵ].

- bugfix: the more\_set\_input\_headers directive might cause invalid  
memory reads because Nginx request header values must be null  
terminated. thanks Maxim D…

- bugfix: removing builtin headers in huge request headers with 20+  
entries could result in data loss. thanks Chris Dumoulin for the patch  
in github issue #6.

You may want to check out the HTML version of this change log here,  
which should look better:

```
http://wiki.nginx.org/HttpHeadersMoreModule#v0.16

```

The ngx\_headers\_more module allows you to add, set, or clear any  
output or input header that you specify. This is an enhanced version  
of the standard headers module because it provides more utilities like  
resetting or clearing “builtin headers” like Content-Type,  
Content-Length, and Server.

You can always get the latest source code from its project page on  
GitHub

[GitHub - openresty/headers-more-nginx-module: Set, add, and clear arbitrary output headers in NGINX http servers](http://github.com/agentzh/headers-more-nginx-module)

and the full documentation from the nginx wiki

[Headers More | NGINX](http://wiki.nginx.org/NginxHttpHeadersMoreModule)

This module is included and enabled by default in our ngx\_openresty  
bundle: [http://openresty.org](http://openresty.org)

Enjoy!  
-agentzh