Nginx-1.5.3

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

*) 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.

Hello!

On Tue, Jul 30, 2013 at 7:49 PM, 卫越 [email protected] 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

It was just wrong that Nginx assumed that truncated upstream responses
to be well formed and complete.

Regards,
-agentzh

Thanks for your reply.

-----邮件原件-----
发件人: [email protected] [mailto:[email protected]] 代表 Yichun
Zhang (agentzh)
发送时间: 2013年7月31日 13:00
收件人: [email protected]
主题: Re: nginx-1.5.3

Hello!

On Tue, Jul 30, 2013 at 7:49 PM, 卫越 [email protected] 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

It was just wrong that Nginx assumed that truncated upstream responses
to be well formed and complete.

Regards,
-agentzh


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

Hello Nginx users,

Now available: Nginx 1.5.3 for Windows Nginx 1.5.3 for Windows – Kevin Worthington (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.

Announcements are also available via my Twitter stream (
http://twitter.com/kworthington), if you prefer to receive updates that
way.

Thank you,
Kevin

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

http://twitter.com/kworthington