# Nginx-1.1.4 **URL:** \ **Category:** NGINX\ **Created:** [September 20, 2011, 1:23pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024 "2011-09-20T13:23:12Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\ **Post date:** [September 20, 2011, 1:23pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/1 "2011-09-20T13:23:12Z")
Changes with nginx 1.1.4 20 Sep 2011 ``` *) Feature: the ngx_http_upstream_keepalive module. *) Feature: the "proxy_http_version" directive. *) Feature: the "fastcgi_keep_conn" directive. *) Feature: the "worker_aio_requests" directive. *) Bugfix: if nginx was built --with-file-aio it could not be run on Linux kernel which did not support AIO. *) Bugfix: in Linux AIO error processing. Thanks to Hagai A.. *) Bugfix: reduced memory consumption for long-lived requests. *) Bugfix: the module ngx_http_mp4_module did not support 64-bit MP4 "co64" atom. ``` – Igor S. ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 20, 2011, 1:40pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/2 "2011-09-20T13:40:34Z")
Hello! On Tue, Sep 20, 2011 at 03:22:25PM +0400, Igor S. wrote: > Changes with nginx 1.1.4 20 Sep 2011 > > ``` > *) Feature: the ngx_http_upstream_keepalive module. > > ``` […] > ``` > *) Bugfix: reduced memory consumption for long-lived requests. > > ``` […] Note to module developers: this release introduces several API changes which may affect 3rd party modules. Please review svn commits for details. Most intresting commits are: [http://trac.nginx.org/nginx/changeset/4115/nginx](http://trac.nginx.org/nginx/changeset/4115/nginx) (ngx\_chain\_update\_chains() api change) [http://trac.nginx.org/nginx/changeset/4117/nginx](http://trac.nginx.org/nginx/changeset/4117/nginx) [http://trac.nginx.org/nginx/changeset/4118/nginx](http://trac.nginx.org/nginx/changeset/4118/nginx) [http://trac.nginx.org/nginx/changeset/4119/nginx](http://trac.nginx.org/nginx/changeset/4119/nginx) [http://trac.nginx.org/nginx/changeset/4120/nginx](http://trac.nginx.org/nginx/changeset/4120/nginx) (various upstream module related changes) Maxim D. ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 20, 2011, 2:12pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/3 "2011-09-20T14:12:48Z")
Thanks to both of you, Boyko ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 20, 2011, 2:53pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/4 "2011-09-20T14:53:03Z")
Hello! On Tue, Sep 20, 2011 at 08:29:06AM -0400, Sirsiwal, Umesh wrote: > Thanks to both of you. Great work. > > If I understand correctly, the only way to use > upstream\_keepalive module is with upstream module. This implies > I cannot use upstream\_keepalive where the upstream is identified > by a variable. For example: > > proxy\_pass http://$host$request\_uri; > > Is my understand correct? Yes. > Is there a way around this restriction? Currently no. Maxim D. ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 20, 2011, 4:06pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/5 "2011-09-20T16:06:45Z")
Great !! finally, upstream\_keepalive is supported!! 2011/9/20 Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 20, 2011, 2:30pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/6 "2011-09-20T14:30:09Z")
Thanks to both of you. Great work. If I understand correctly, the only way to use upstream\_keepalive module is with upstream module. This implies I cannot use upstream\_keepalive where the upstream is identified by a variable. For example: proxy\_pass http://$host$request\_uri; Is my understand correct? Is there a way around this restriction? -Umesh * * * From: removed\_email\_address@domain.invalid [removed\_email\_address@domain.invalid] On Behalf Of Boyko Y. [removed\_email\_address@domain.invalid] Sent: Tuesday, September 20, 2011 8:12 AM To: removed\_email\_address@domain.invalid Cc: removed\_email\_address@domain.invalid Subject: Re: nginx-1.1.4 Thanks to both of you, Boyko * * * nginx mailing list removed\_email\_address@domain.invalid [http://mailman.nginx.org/mailman/listinfo/nginx](http://mailman.nginx.org/mailman/listinfo/nginx) ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 21, 2011, 12:21pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/7 "2011-09-21T12:21:25Z")
Hello! On Wed, Sep 21, 2011 at 02:58:59AM -0700, Geoge.Q wrote: > When is it ported to stable version? I means the upstream keep-alive feature? Most likely never: there are several API changes which are required for this. Breaking API in stable is a bad thing. Maxim D. ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 21, 2011, 12:26pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/8 "2011-09-21T12:26:59Z")
On Sep 21, 2011, at 14:20 , Maxim D. wrote: > Hello! > > On Wed, Sep 21, 2011 at 02:58:59AM -0700, Geoge.Q wrote: > > > When is it ported to stable version? I means the upstream keep-alive feature? > > Most likely never: there are several API changes which are > required for this. Breaking API in stable is a bad thing. At some point 1.1.x will just become stable 🙂 – Igor S. > **[Igor Sysoev](http://sysoev.ru/en/)** ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 21, 2011, 12:52pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/9 "2011-09-21T12:52:21Z")
On 21.09.2011 13:26, Igor S. wrote: > > > When is it ported to stable version? I means the upstream keep-alive feature? > > > > Most likely never: there are several API changes which are > > required for this. Breaking API in stable is a bad thing. > > At some point 1.1.x will just become stable 🙂 major.minor.revision nginx will not use odd minor version numbers to denote development releases and even minor version numbers to denote stable releases? 1.0.x - stable branch 1.1.x - devel branch 1.2.x - stable branch 1.3.x - devel branch and so on? if not - it will be many confusion, which version 1.1.x is stable, and which nginx 1.2.x version is devel or stable. use odd minor version numbers to denote development releases and even minor version numbers to denote stable releases - imho is very useful and clear version numbering scheme. (but looks like apache/squid/haproxy not use this scheme) – Best regards, Gena ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 21, 2011, 1:11pm UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/10 "2011-09-21T13:11:32Z")
Hello! On Wed, Sep 21, 2011 at 01:51:34PM +0300, Gena M. wrote: > if not - it will be many confusion, which version 1.1.x is stable, > and which nginx 1.2.x version is devel or stable. > > use odd minor version numbers to denote development releases > and even minor version numbers to denote stable releases - > imho is very useful and clear version numbering scheme. Yes, I’ve already proposed this to Igor to simplify stable vs. devel distinction. He isn’t convinced yet, but we have some time to think about this. Maxim D. ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 21, 2011, 11:59am UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/11 "2011-09-21T11:59:42Z")
When is it ported to stable version? I means the upstream keep-alive feature? Thanks George 2011/9/20, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > > > Maxim D. > > * * * > > nginx mailing list > [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > [mailman.nginx.org archive](http://mailman.nginx.org/mailman/listinfo/nginx) – ҵƶ豸 ---
**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\ **Post date:** [September 22, 2011, 3:11am UTC](https://www.ruby-forum.com/t/nginx-1-1-4/212024/12 "2011-09-22T03:11:07Z")
Hello Nginx U.s, I just released Nginx 1.1.4 For Windows [Nginx 1.1.4 for Windows – Kevin Worthington](http://goo.gl/WzEeA) (32-bit and 64-bit) These versions are to support legacy users who are already using Cygwin based builds of Nginx. Official Windows binaries are at [nginx.org](http://nginx.org) ## Thanks, Kevin Kevin W. kworthington (at] gmail {dot) com