# Nginx-1.5.3 **URL:** \ **Category:** NGINX\ **Created:** [July 30, 2013, 3:41pm UTC](https://www.ruby-forum.com/t/nginx-1-5-3/236011 "2013-07-30T15:41:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\ **Post date:** [July 30, 2013, 3:41pm UTC](https://www.ruby-forum.com/t/nginx-1-5-3/236011/1 "2013-07-30T15:41:48Z")
Changes with nginx 1.5.3 30 Jul 2013 ``` *) Change in internal API: now u->length defaults to -1 if working ``` with backends in unbuffered mode. ``` *) Change: now after receiving an incomplete response from a backend server nginx tries to send an available part of the response to a client, and then closes client connection. *) Bugfix: a segmentation fault might occur in a worker process if ``` the ngx\_http\_spdy\_module was used with the “client\_body\_in\_file\_only” directive. ``` *) Bugfix: the "so_keepalive" parameter of the "listen" directive ``` might be handled incorrectly on DragonFlyBSD. Thanks to Sepherosa Ziehau. ``` *) Bugfix: in the ngx_http_xslt_filter_module. *) Bugfix: in the ngx_http_sub_filter_module. ``` – Maxim D. [http://nginx.org/en/donation.html](http://nginx.org/en/donation.html) ---
**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:** [July 31, 2013, 4:50am UTC](https://www.ruby-forum.com/t/nginx-1-5-3/236011/2 "2013-07-31T04:50:04Z")
> \*) Change: now after receiving an incomplete response from a backend > server nginx tries to send an available part of the response to a > client, and then closes client connection. It is obviously different from previous nginx, but I wonder why nginx made this change. ---
**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:** [July 31, 2013, 7:00am UTC](https://www.ruby-forum.com/t/nginx-1-5-3/236011/3 "2013-07-31T07:00:21Z")
Hello! On Tue, Jul 30, 2013 at 7:49 PM, 卫越 [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > \*) Change: now after receiving an incomplete response from a backend > > server nginx tries to send an available part of the response to a > > client, and then closes client connection. > > It is obviously different from previous nginx, but I wonder why nginx made > this change. I originally proposed this change here: [[PATCH] Make ngx\_http\_upstream provide a way to expose errors after sending out the response header](http://mailman.nginx.org/pipermail/nginx-devel/2012-September/002693.html) It was just wrong that Nginx assumed that truncated upstream responses to be well formed and complete. Regards, -agentzh ---
**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:** [August 1, 2013, 4:21am UTC](https://www.ruby-forum.com/t/nginx-1-5-3/236011/4 "2013-08-01T04:21:51Z")
Thanks for your reply. -----邮件原件----- 发件人: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] 代表 Yichun Zhang (agentzh) 发送时间: 2013年7月31日 13:00 收件人: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 主题: Re: nginx-1.5.3 Hello! On Tue, Jul 30, 2013 at 7:49 PM, 卫越 [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > \*) Change: now after receiving an incomplete response from a backend > > server nginx tries to send an available part of the response to a > > client, and then closes client connection. > > It is obviously different from previous nginx, but I wonder why nginx made > this change. I originally proposed this change here: [[PATCH] Make ngx\_http\_upstream provide a way to expose errors after sending out the response header](http://mailman.nginx.org/pipermail/nginx-devel/2012-September/002693.html) It was just wrong that Nginx assumed that truncated upstream responses to be well formed and complete. Regards, -agentzh * * * nginx mailing list [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > **[mailman.nginx.org archive](http://mailman.nginx.org/pipermail/)** ---
**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:** [August 3, 2013, 6:55pm UTC](https://www.ruby-forum.com/t/nginx-1-5-3/236011/5 "2013-08-03T18:55:26Z")
Hello Nginx users, Now available: Nginx 1.5.3 for Windows [Nginx 1.5.3 for Windows – Kevin Worthington](http://goo.gl/qiz6kq) (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 via my Twitter stream ( [http://twitter.com/kworthington](http://twitter.com/kworthington)), if you prefer to receive updates that way. ## 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)