# Nginx-1.3.0 **URL:** \ **Category:** NGINX\ **Created:** [May 15, 2012, 4:40pm UTC](https://www.ruby-forum.com/t/nginx-1-3-0/219761 "2012-05-15T16:40:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Gurdipe\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@Gurdipe\_D](https://www.ruby-forum.com/u/Gurdipe_D)\ **Post date:** [May 15, 2012, 4:40pm UTC](https://www.ruby-forum.com/t/nginx-1-3-0/219761/1 "2012-05-15T16:40:45Z")
Changes with nginx 1.3.0 15 May 2012 ``` *) Feature: the "debug_connection" directive now supports IPv6 ``` addresses and the “unix:” parameter. ``` *) Feature: the "set_real_ip_from" directive and the "proxy" ``` parameter of the “geo” directive now support IPv6 addresses. ``` *) Feature: the "real_ip_recursive", "geoip_proxy", and "geoip_proxy_recursive" directives. *) Feature: the "proxy_recursive" parameter of the "geo" directive. *) Bugfix: a segmentation fault might occur in a worker process if ``` the “resolver” directive was used. ``` *) Bugfix: a segmentation fault might occur in a worker process if ``` the “fastcgi\_pass”, “scgi\_pass”, or “uwsgi\_pass” directives were used and backend returned incorrect response. ``` *) Bugfix: a segmentation fault might occur in a worker process if ``` the “rewrite” directive was used and new request arguments in a replacement used variables. ``` *) Bugfix: nginx might hog CPU if the open file resource limit was reached. *) Bugfix: nginx might loop infinitely over backends if the "proxy_next_upstream" directive with the "http_404" parameter was used and there were backup servers specified in an upstream ``` block. ``` *) Bugfix: adding the "down" parameter of the "server" directive ``` might cause unneeded client redistribution among backend servers if the “ip\_hash” directive was used. ``` *) Bugfix: socket leak. Thanks to Yichun Z.. *) Bugfix: in the ngx_http_fastcgi_module. ``` Maxim D. ---
**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:** [May 16, 2012, 12:14am UTC](https://www.ruby-forum.com/t/nginx-1-3-0/219761/2 "2012-05-16T00:14:04Z")
Hello Nginx U.s, Now available: Nginx 1.3.0 For Windows [Nginx 1.3.0 for Windows – Kevin Worthington](http://goo.gl/v9xkC) (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). ## 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) On 5/15/12, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > ``` > *) Feature: the "real_ip_recursive", "geoip_proxy", and > backend returned incorrect response. > used and there were backup servers specified in an upstream block. > > ``` > > 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) ## – Best regards, Kevin Kevin W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > **[Kevin Worthington](https://kevinworthington.com/)** > > Practical Tech Guides, Troubleshooting, and Insights on the Modern Internet (516) 647-1992 [http://twitter.com/kworthington](http://twitter.com/kworthington) ---
**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:** [May 16, 2012, 10:06am UTC](https://www.ruby-forum.com/t/nginx-1-3-0/219761/3 "2012-05-16T10:06:22Z")
2012/5/15 Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > Changes with nginx 1.3.0 15 May 2012 … > \*) Bugfix: in the ngx\_http\_fastcgi\_module. Could you please elaborate this ? is 1.2.x brach affected ? Thank you very much. ---
**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:** [May 16, 2012, 10:21am UTC](https://www.ruby-forum.com/t/nginx-1-3-0/219761/4 "2012-05-16T10:21:53Z")
Hello! On Wed, May 16, 2012 at 10:05:02AM +0200, Daniel C. wrote: > 2012/5/15 Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > > Changes with nginx 1.3.0 15 May 2012 > > … > > > \*) Bugfix: in the ngx\_http\_fastcgi\_module. > > Could you please elaborate this ? [http://trac.nginx.org/nginx/changeset/4617/nginx](http://trac.nginx.org/nginx/changeset/4617/nginx) In short: some FastCGI records wasn’t correcly handled if padding was used on them (which almost never happens as these records are naturally aligned). > is 1.2.x brach affected ? Yes, as 1.3.0 is first release after 1.2.0. Maxim D.