# Nginx-1.9.11

**URL:** <https://www.ruby-forum.com/t/nginx-1-9-11/244029>\
**Category:** NGINX\
**Created:** [February 9, 2016, 3:29pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029 "2016-02-09T15:29:53Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [February 9, 2016, 3:29pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/1 "2016-02-09T15:29:53Z")

</div>

Changes with nginx 1.9.11 09 Feb  
2016

```
*) Feature: TCP support in resolver.

*) Feature: dynamic modules.

*) Bugfix: the $request_length variable did not include size of 

```

request  
headers when using HTTP/2.

```
*) Bugfix: in the ngx_http_v2_module.

```

–  
Maxim D.  
[http://nginx.org/](http://nginx.org/)

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 4:18pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/2 "2016-02-09T16:18:22Z")

</div>

Hi

starting wit a running nginx/1.9.10 on linux/64

simple build/upgrade to nginx/1.9.11; same config as before

no errors in build

nginx -v  
nginx version: nginx/1.9.11

but,

systemctl start  
nginx.serviceJob for nginx.service failed. See “systemctl status  
nginx.service” and “journalctl -xn” for details.

systemctl status nginx.service -l  
nginx.service - The nginx HTTP and reverse proxy server  
Loaded: loaded (/etc/systemd/system/nginx.service; enabled)  
Active: failed (Result: signal) since Tue 2016-02-09 07:09:47  
PST; 24s ago  
Process: 4509 ExecStartPre=/usr/local/sbin/nginx -t -c  
/usr/local/etc/nginx/nginx.conf (code=killed, signal=FPE)  
Main PID: 7589 (code=exited, status=0/SUCCESS)

nginx -t -c /usr/local/etc/nginx/nginx.conf  
Floating point exception

in syslog

Feb 9 07:11:07 jimsweb kernel: [393917.665398] traps: nginx[4679]  
trap divide error ip:41a95e sp:7ffef4fcbd00 error:0 in  
nginx[400000+ed000]

dropback to 1.9.10 works fine

if there’s other info that’ll help, let me know.

Jim

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 4:41pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/3 "2016-02-09T16:41:44Z")

</div>

It’s brotli.

Removing

–add-module=/usr/local/src/ngx\_brotli

from 1.9.11 config, rebuilding, it’s fixed. Runs ok.

brotli’s OK atm with 1.9.10, but not with 1.9.11

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 5:56pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/4 "2016-02-09T17:56:31Z")

</div>

On Tuesday 09 February 2016 11:53:15 locojohn wrote:

> I experience the same issue, but I do not have the module reported by  
> anonymous user installed:
> 
> system:~#nginx -t  
> Floating point exception
> 
> dmesg:  
> [659221.307369] traps: nginx[20028] trap divide error ip:422fba  
> sp:7ffd8c72a8a0 error:0 in nginx[400000+95d000]

What 3rd-party modules do you have instead? Please, try without them.

wbr, Valentin V. Bartenev

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 5:53pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/5 "2016-02-09T17:53:36Z")

</div>

I experience the same issue, but I do not have the module reported by  
anonymous user installed:

system:~#nginx -t  
Floating point exception

dmesg:  
[659221.307369] traps: nginx[20028] trap divide error ip:422fba  
sp:7ffd8c72a8a0 error:0 in nginx[400000+95d000]

Posted at Nginx Forum:

> **[Re: nginx-1.9.11 -- "Floating point exception" on exec after upgrading 1.9.10...](https://forum.nginx.org/read.php?2,264422,264434#msg-264434)**
>
> Changes with nginx 1.9.11 09 Feb 2016 \*) Feature: TCP support in resolver. \*) Feature: dynamic modules. \*) Bugfix: the $request\_length variable did not include size of request headers when using HT

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 6:01pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/6 "2016-02-09T18:01:12Z")

</div>

It crashes with pagespeed module now. 1.9.10 was working fine.

Andrejs.

Posted at Nginx Forum:

> **[Re: nginx-1.9.11 -- "Floating point exception" on exec after upgrading 1.9.10...](https://forum.nginx.org/read.php?2,264422,264436#msg-264436)**
>
> Changes with nginx 1.9.11 09 Feb 2016 \*) Feature: TCP support in resolver. \*) Feature: dynamic modules. \*) Bugfix: the $request\_length variable did not include size of request headers when using HT

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 9:00pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/7 "2016-02-09T21:00:32Z")

</div>

Maxim D.:

> Changes with nginx 1.9.11 09 Feb 2016
> 
> ```
> *) Feature: TCP support in resolver.
> 
> ```

the rDNS module ([F5 NGINX Product Documentation](https://www.nginx.com/resources/wiki/modules/rdns/))  
don’t compile anymore

cc -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security  
-Wall -I src/core -I src/event -I src/event/modules -I src/os/unix  
-I objs -I src/http -I src/http/modules -I src/http/v2 -I src/mail   
-o objs/addon/nginx-http-rdns-20140411/ngx\_http\_rdns\_module.o   
./nginx-http-rdns-20140411//ngx\_http\_rdns\_module.c  
./nginx-http-rdns-20140411//ngx\_http\_rdns\_module.c: In function  
‘merge\_loc\_conf’:  
./nginx-http-rdns-20140411//ngx\_http\_rdns\_module.c:217:89: error:  
‘ngx\_resolver\_t’ has no member named ‘udp\_connections’  
if (conf-\>conf.enabled && ((core\_loc\_cf-\>resolver == NULL) ||  
(core\_loc\_cf-\>resolver-\>udp\_connections.nelts == 0))) {

```
                ^

```

make[2]: \*\*\*  
[objs/addon/nginx-http-rdns-20140411/ngx\_http\_rdns\_module.o] Error 1

unrelated to above:  
attached a patch to correct a manpage warning (not new in this version)

Andreas

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 9:42pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/8 "2016-02-09T21:42:36Z")

</div>

On Tue, Feb 09, 2016 at 08:59:42PM +0100, A. Schulze wrote:

> cc -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall  
> ^  
> make[2]: \*\*\* [objs/addon/nginx-http-rdns-20140411/ngx\_http\_rdns\_module.o]  
> Error 1

“connections” should be used instead of “udp\_connections”.

[..]

–  
Roman A.

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 9:05pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/9 "2016-02-09T21:05:48Z")

</div>

## A. Schulze Wrote:

> Maxim D.:
> 
> > Changes with nginx 1.9.11 09  
> > Feb 2016
> > 
> > ```
> > *) Feature: TCP support in resolver.
> > 
> > ```
> 
> the rDNS module ([F5 NGINX Product Documentation](https://www.nginx.com/resources/wiki/modules/rdns/))  
> don’t compile anymore

It breaks udp in (openresty)Lua as well.

Posted at Nginx Forum:  
[https://forum.nginx.org/read.php?2,264422,264444#msg-264444](https://forum.nginx.org/read.php?2,264422,264444#msg-264444)

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 9, 2016, 10:32pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/10 "2016-02-09T22:32:15Z")

</div>

Roman A.:

> > compile anymore  
> > if (conf-\>conf.enabled && ((core\_loc\_cf-\>resolver == NULL) ||  
> > (core\_loc\_cf-\>resolver-\>udp\_connections.nelts == 0))) {  
> > ^  
> > make[2]: \*\*\* [objs/addon/nginx-http-rdns-20140411/ngx\_http\_rdns\_module.o]  
> > Error 1
> 
> “connections” should be used instead of “udp\_connectionss”

Roman,

thanks for the hint. The attached patch solve at least the compile  
error.  
(still untested if the module still work)

Andreas

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 10, 2016, 9:13am UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/11 "2016-02-10T09:13:06Z")

</div>

Hello Nginx users,

Now available: Nginx 1.9.11 for Windows  
[Nginx 1.9.11 for Windows – Kevin Worthington](https://kevinworthington.com/nginxwin1911) (32-bit and 64-bit versions)

These versions are to support legacy users who are already using Cygwin  
based builds of Nginx. Officially supported native Windows binaries are  
at  
[nginx.org](http://nginx.org).

Announcements are also available here:  
Twitter [http://twitter.com/kworthington](http://twitter.com/kworthington)  
Google+ [Google Workspace Updates: New community features for Google Chat and an update on Currents](https://plus.google.com/+KevinWorthington/)

## Thank you, Kevin

Kevin W.  
kworthington _@_ (gmail] [dot} {com)

> **[Kevin Worthington](https://kevinworthington.com/)**
>
> Practical Tech Guides, Troubleshooting, and Insights on the Modern Internet

[http://twitter.com/kworthington](http://twitter.com/kworthington)

> **[Google Workspace Updates: New community features for Google Chat and an...](https://workspaceupdates.googleblog.com/2023/04/new-community-features-for-google-chat-and-an-update-currents%20.html)**

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 10, 2016, 11:02am UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/12 "2016-02-10T11:02:20Z")

</div>

I also get a compile error related to Pagespeed:

```
            -o objs/addon/src/ngx_message_handler.o \

```

/root/ngx\_pagespeed-release-1.10.33.4-beta/src/ngx\_message\_handler.cc  
cc -c -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror  
-g  
-march=i686 -D\_GLIBCXX\_USE\_CXX11\_ABI=0 -I src/core -I src/event -I  
src/event/modules -I src/os/unix -I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include -I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/chromium/src  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/google-sparsehash/src  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/google-sparsehash/gen/arch/linux/ia32/include  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/protobuf/src  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/re2/src  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/out/Debug/obj/gen  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/out/Debug/obj/gen/protoc\_out/instaweb  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/apr/src/include  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/aprutil/src/include  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/apr/gen/arch/linux/ia32/include  
-I  
/root/ngx\_pagespeed-release-1.10.33.4-beta/psol/include/third\_party/aprutil/gen/arch/linux/ia32/include  
-I /usr/include/libxml2 -I objs -I src/http -I src/http/modules -I  
src/http/v2 -I src/mail   
-o objs/addon/src/ngx\_pagespeed.o \

/root/ngx\_pagespeed-release-1.10.33.4-beta/src/ngx\_pagespeed.cc  
/root/ngx\_pagespeed-release-1.10.33.4-beta/src/ngx\_pagespeed.cc:3133:1:  
error: deprecated conversion from string constant to ‘char\*’  
[-Werror=write-strings]  
};  
^  
/root/ngx\_pagespeed-release-1.10.33.4-beta/src/ngx\_pagespeed.cc:3148:1:  
error: deprecated conversion from string constant to ‘char\*’  
[-Werror=write-strings]  
};  
^  
cc1plus: all warnings being treated as errors  
make[1]: \*\*\* [objs/addon/src/ngx\_pagespeed.o] Error 1  
make[1]: Leaving directory `/root/temp/nginx-1.9.11’  
make: \*\*\* [build] Error 2

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 10, 2016, 2:01pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/13 "2016-02-10T14:01:06Z")

</div>

Hello!

On Wed, Feb 10, 2016 at 12:15:53PM +0100, Lukas T. wrote:

> Apply this patch:  
> [hg.nginx.org is decommissioned](http://hg.nginx.org/nginx/rev/ff1e625ae55b)
> 
> Or pull latest source code from the repository.

Trivial workaround for build failures due to warnings is to use  
-Wno-error, e.g.:

./configure --with-cc-opt=“-Wno-error” …

In this particular case, -Wno-write-strings can be used instead,  
e.g.:

./configure --with-cc-opt=“-Wno-write-strings” …

–  
Maxim D.

> **[nginx](http://nginx.org/)**

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 11, 2016, 3:31am UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/14 "2016-02-11T03:31:19Z")

</div>

I’m having issues with 1.9.11. With the exact same build configuration  
as I  
used for 1.9.10, and the exact same config files for nginx - I am now  
getting this when I run nginx -t at the command-line:

nginx: [emerg] unknown directive “charset” in /etc/nginx/nginx.conf:62  
nginx: configuration file /etc/nginx/nginx.conf test failed

When I comment out that particular line in the nginx.conf file, I am  
then  
presented with another error:

nginx: [emerg] unknown directive “add\_header” in /etc/nginx/ssl.conf:28  
nginx: configuration file /etc/nginx/nginx.conf test failed

Not sure why I’m observing this behavior, when the exact same build  
configuration for 1.9.10 worked just fine. It seems like some of the  
core  
modules (e.g.: ngx\_http\_charset\_module, ngx\_http\_headers\_module) are  
somehow  
missing from my build? Am I missing something? These are the  
module-related flags I provide to “./configure”:

–with-pcre-jit   
–with-ipv6   
–with-file-aio   
–with-http\_ssl\_module   
–with-http\_v2\_module   
–with-http\_realip\_module   
–without-http\_map\_module   
–without-http\_memcached\_module   
–without-http\_autoindex\_module   
–without-http\_split\_clients\_module   
–without-http\_upstream\_ip\_hash\_module   
–without-http\_upstream\_least\_conn\_module   
–without-http\_upstream\_keepalive\_module   
–without-http\_userid\_module   
–without-http\_empty\_gif\_module   
–without-http\_auth\_basic\_module   
–without-mail\_pop3\_module   
–without-mail\_smtp\_module   
–without-mail\_imap\_module   
–without-http\_uwsgi\_module   
–without-http\_scgi\_module   
–without-http\_browser\_module   
–add-module=$HOME/naxsi-${NAXSI\_VER}/naxsi\_src   
–add-module=$HOME/ngx\_pagespeed-${PAGESPEED\_VER}-beta

Posted at Nginx Forum:

> **[Re: nginx-1.9.11](https://forum.nginx.org/read.php?2,264422,264481#msg-264481)**
>
> Changes with nginx 1.9.11 09 Feb 2016 \*) Feature: TCP support in resolver. \*) Feature: dynamic modules. \*) Bugfix: the $request\_length variable did not include size of request headers when using HT

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 10, 2016, 12:16pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/15 "2016-02-10T12:16:32Z")

</div>

> I also get a compile error related to Pagespeed:  
> […]  
> /root/ngx\_pagespeed-release-1.10.33.4-beta/src/ngx\_pagespeed.cc:3148:1:  
> error: deprecated conversion from string constant to char\*  
> [-Werror=write-strings]  
> };  
> ^  
> cc1plus: all warnings being treated as errors

Apply this patch:

> **[hg.nginx.org is decommissioned](http://hg.nginx.org/nginx/rev/ff1e625ae55b)**

Or pull latest source code from the repository.

Regards,

Lukas

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 11, 2016, 9:40am UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/16 "2016-02-11T09:40:40Z")

</div>

> ./configure --with-cc-opt=“-Wno-write-strings” …

When I tried this, I get:

Starting nginx: nginx: [emerg] unknown directive “charset” in  
/etc/nginx/nginx.conf:15  
nginx: configuration file /etc/nginx/nginx.conf test failed

* * *

But I just saw your other reply re the ngx\_pagespeed changeset, so  
that’s  
what I’ll look into

Posted at Nginx Forum:  
[https://forum.nginx.org/read.php?2,264422,264484#msg-264484](https://forum.nginx.org/read.php?2,264422,264484#msg-264484)

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 13, 2016, 7:20pm UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/17 "2016-02-13T19:20:05Z")

</div>

A. Schulze:

> The attached patch solve at least the compile error.  
> now also verified the module work with nginx-1.9.11

Andreas

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 11, 2016, 4:08am UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/18 "2016-02-11T04:08:07Z")

</div>

Hello!

On Wed, Feb 10, 2016 at 09:30:49PM -0500, qbitx wrote:

> nginx: [emerg] unknown directive “add\_header” in /etc/nginx/ssl.conf:28  
> nginx: configuration file /etc/nginx/nginx.conf test failed
> 
> Not sure why I’m observing this behavior, when the exact same build  
> configuration for 1.9.10 worked just fine. It seems like some of the core  
> modules (e.g.: ngx\_http\_charset\_module, ngx\_http\_headers\_module) are somehow  
> missing from my build? Am I missing something? These are the  
> module-related flags I provide to “./configure”:

[…]

> –add-module=$HOME/naxsi-${NAXSI\_VER}/naxsi\_src   
> –add-module=$HOME/ngx\_pagespeed-${PAGESPEED\_VER}-beta

Most likely this is ngx\_pagespeed 3rd party module which causes  
the problem you are seeing. It tries to do unsupported  
modifications of order of modules, and was beaten by internal  
changes in configure scripts in 1.9.11. Quick look suggests the  
problem is expected to be fixed by this changeset:

> <https://github.com/apache/incubator-pagespeed-ngx/commit/daa6031294403a25a4fd2f4c7b6a16a349df8af2>
>
> Signed-off-by: Piotr Sikora \<piotrsikora@google.com\>

That is, either update ngx\_pagespeed to the latest git checkout,  
or compile nginx without it.

–  
Maxim D.

> **[nginx](http://nginx.org/)**

---

<div class="post-metadata">

**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\
**Post date:** [February 18, 2016, 9:32am UTC](https://www.ruby-forum.com/t/nginx-1-9-11/244029/19 "2016-02-18T09:32:19Z")

</div>

With the release of ngx\_pagespeed 1.10.33.5, I’m no longer having any  
make  
issues with 1.9.11

Posted at Nginx Forum:

> **[Re: nginx-1.9.11 -- "Floating point exception" on exec after upgrading 1.9.10...](https://forum.nginx.org/read.php?2,264422,264581#msg-264581)**
>
> Changes with nginx 1.9.11 09 Feb 2016 \*) Feature: TCP support in resolver. \*) Feature: dynamic modules. \*) Bugfix: the $request\_length variable did not include size of request headers when using HT