Nginx-1.5.10

Changes with nginx 1.5.10 04 Feb
2014

*) Feature: the ngx_http_spdy_module now uses SPDY 3.1 protocol.
   Thanks to Automattic and MaxCDN for sponsoring this work.

*) Feature: the ngx_http_mp4_module now skips tracks too short for a
   seek requested.

*) Bugfix: a segmentation fault might occur in a worker process if 

the
$ssl_session_id variable was used in logs; the bug had appeared
in
1.5.9.

*) Bugfix: the $date_local and $date_gmt variables used wrong format
   outside of the ngx_http_ssi_filter_module.

*) Bugfix: client connections might be immediately closed if 

deferred
accept was used; the bug had appeared in 1.3.15.

*) Bugfix: alerts "getsockopt(TCP_FASTOPEN) ... failed" appeared in 

logs
during binary upgrade on Linux; the bug had appeared in 1.5.8.
Thanks to Piotr S…


Maxim D.
http://nginx.org/en/donation.html

On Tue, 2014-02-04 at 17:45 +0400, Maxim D. wrote:

   1.5.9.

Great to hear about the new speedy stuff. I take it it’s not getting
backported into 1.4, so when’s 1.6 due?

Cheers,

Steve


Steve H. BSc(Hons) MIITP
http://www.greengecko.co.nz
Linkedin: http://www.linkedin.com/in/steveholdoway
Skype: sholdowa

Hi!

On Feb 4, 2014, at 5:31 PM, Steve H. [email protected]
wrote:

  $ssl_session_id variable was used in logs; the bug had appeared in
  Thanks to Piotr S..

Great to hear about the new speedy stuff. I take it it’s not getting
backported into 1.4, so when’s 1.6 due?

mid-year :slight_smile:

On Wednesday 05 February 2014 14:31:01 Steve H. wrote:
[…]

Great to hear about the new speedy stuff. I take it it’s not getting
backported into 1.4, so when’s 1.6 due?

Just a note for people who worry about using mainline version in
production.
The fact that there is version called “stable” doesn’t imply that the
other one
is “unstable”. We call one branch stable because we maintain internal
API and
feature set stability for 3rd-party developers, while mainline versions
gets
all improvements (and even more bugfixes).

wbr, Valentin V. Bartenev

Hi Valentin,

Thanks for that information.
However, since the usual way to do things is to have 2 branches:
production
& development, I guess the awaited people initial reaction is not to
trust
the ‘mainline’ branch.
I think it would be highly beneficial to mention somewhere (on the
downloads page?) that the mainline branch is production-ready.

Production managers are traditionally scared, so repeating and enforcing
the message would be highly beneficial. ;o)

B. R.

Hello Nginx users,

Now available: Nginx 1.5.10 for Windows http://goo.gl/OCUvut (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 Twitter (
http://twitter.com/kworthington), if you prefer to receive updates that
way.

Thank you,
Kevin

Kevin W.
kworthington @ (gmail] [dot} {com)
http://kevinworthington.com/
http://twitter.com/kworthington

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs