Nginx 1.2.0 (stable) released

by conductor • 14 years ago

87 23 14 years ago

AncientPC• 14 years ago

Changelog: http://nginx.org/en/CHANGES-1.2

Differences between v1.1.19 and v1.2:

  Changes with nginx 1.2.0                                         23 Apr 2012

    *) Bugfix: a segmentation fault might occur in a worker process if the
       "try_files" directive was used; the bug had appeared in 1.1.19.

    *) Bugfix: response might be truncated if there were more than IOV_MAX
       buffers used.

    *) Bugfix: in the "crop" parameter of the "image_filter" directive.
       Thanks to Maxim Bublis.

Jonanin• 14 years ago

I thought maybe the "1.2.0" version number meant some new features, but I checked the CHANGES file and it's just three bugfixes; they just have an odd version numbering scheme.

mattparlane2• 14 years ago

They use the (fairly common) scheme where odd-numbered point releases are development and even-numbered point releases are (declared) stable, so there is actually a lot in this. Check all the "Feature:" lines in the 1.1.x versions.

cbsmith• 14 years ago

Compared to the 1.0.x branch, there are a lot of new features.

bostonvaulter2• 14 years ago

But unfortunately they are not summarized anywhere.

moonboots4• 14 years ago

In terms of diffs, nginx 1.2.0 adds only a few bugfixes to the 1.1.19 release. However, this release is significant in that it marks the 1.1.x dev branch to stable.

The main feature of the 1.1.x branch I've used is http/1.1 reverse proxying. Previously in 1.0, nginx spoke http/1.0 with reverse proxies. This upgrade allows nginx to make persistent connections with backend servers instead of creating new connections whenever it forward requests.

derefr• 14 years ago

Interesting--does the above-mentioned feature mean that nginx can finally be put in front of a websocket server (e.g., socket.io)?

AUmrysh• 14 years ago

I think it's capable of doing this, but I read that you have to disable the http proxy cache or something similar.

edit: that's for version 1.0.X though, not sure about 1.1

pippy• 14 years ago

This is fantastic, I was just talking about this on HN a few days ago: http://news.ycombinator.com/reply?id=3865966&whence=thre...

moonboots4• 14 years ago

I'm not sure if understanding HTTP/1.1 is enough to bridge a websocket connection between client and backend websocket server. However, there is a 3rd party tcp proxy module for nginx that allows proxying websockets:

https://github.com/yaoweibin/nginx_tcp_proxy_module

nilsbunger2• 14 years ago

Anyone know what the diffs are between the last STABLE release (1.0.15) and 1.2.0? If you're in production, isn't that the path you'd be following?

Surprisingly I can't seem to find that info.

moonboots4• 14 years ago

Unfortunately these changes aren't summarized. The differences are all the 'feature' bullets in the changes webpage from 1.1.0 to 1.2.0. I've assembled these below:

  - the $connection_requests variable.
  - $tcpinfo_rtt, $tcpinfo_rttvar, $tcpinfo_snd_cwnd and $tcpinfo_rcv_space variables.  
  - the "worker_cpu_affinity" directive now works on FreeBSD.
  - the "xslt_param" and "xslt_string_param" directives.  Thanks to Samuel Behan.  
  - the "from" parameter of the "disable_symlinks" directive.
  - the "return" and "error_page" directives can now be used to return 307 redirections.  
  - the "disable_symlinks" directive.
  - the "proxy_cookie_domain" and "proxy_cookie_path" directives.  
  - multiple "limit_req" limits may be used simultaneously.
  - the "TLSv1.1" and "TLSv1.2" parameters of the "ssl_protocols" directive.  
  - the "proxy/fastcgi/scgi/uwsgi_cache_lock", "proxy/fastcgi/scgi/uwsgi_cache_lock_timeout" directives.  
  - the "pcre_jit" directive.
  - the "if" SSI command supports captures in regular expressions.  
  - the "so_keepalive" parameter of the "listen" directive.  Thanks to Vsevolod Stakhov.  
  - the "if_not_empty" parameter of the "fastcgi/scgi/uwsgi_param" directives.  
  - the $https variable.
  - the "proxy_redirect" directive supports variables in the first parameter.
  - the "proxy_redirect" directive supports regular expressions.  
  - the "valid" parameter of the "resolver" directive. By default TTL returned by a DNS server is used.
  - support for multiple "limit_conn" limits on the same level.  
  - the "image_filter_sharpen" directive.  
  - support of several DNS servers in the "resolver" directive.  Thanks to Kirill A. Korinskiy.
  - "proxy/fastcgi/scgi/uwsgi_ignore_headers" directives support the following additional values: X-Accel-Limit-Rate,
  - decrease of memory consumption if SSL is used.  
  - the "uwsgi_buffering" and "scgi_buffering" directives.  Thanks to Peter Smit.
  - the ngx_http_upstream_keepalive module.  
  - the "proxy_http_version" directive.  
  - the "fastcgi_keep_conn" directive.  
  - the "worker_aio_requests" directive.  
  - the module ngx_http_mp4_module.  
  - the "max_ranges" directive.  
  - now shared zones and caches use POSIX semaphores on Solaris.  Thanks to Den Ivanov.
  - accept filters are now supported on NetBSD.  
  - cache loader run time decrease.  
  - "loader_files", "loader_sleep", and "loader_threshold" options of the "proxy/fastcgi/scgi/uwsgi_cache_path" directives.
  - loading time decrease of configuration with large number of HTTPS sites.
  - now nginx supports ECDHE key exchange ciphers.  Thanks to Adrian Kotelba.
  - the "lingering_close" directive.  Thanks to Maxim Dounin.

patrickaljord• 14 years ago

In case you're wondering like me, SPDY is planed for the next 1.3 version according to their trac milestone http://trac.nginx.org/nginx/milestone/1.3.0

mdesantis• 14 years ago

as WebSockets too

HeroNote• 14 years ago

Free Nginx ebook update: http://www.heronote.com/files/nginx.htm

mh-• 14 years ago

no PDF?

mattparlane2• 14 years ago

That looks like a really useful resource, but seriously -- EXE or CHM files? I would have thought that a huge chunk of the people likely to be deploying nginx would be on either OSX or Linux machines...

mrweasel• 14 years ago

That does seem a bit weird. Anyway the Nginx manual is quite good in it self. Before setting up our production boxes I read through most of the manual and so fare I have yet to encounter any issue that I could figure out using just the manual.

Nginx 1.2.0 (stable) released

Related Stories