Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nginx 1.2.0 (stable) released

nginx.org

Post reply on HN
Print view View original

11–20 of 24 posts

Re: Nginx 1.2.0 (stable) released

#11

Post by moonboots »

derefr wrote: post #7
moonboots wrote: post #5

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 wh…

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

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

Re: Nginx 1.2.0 (stable) released

#14

Post by nilsbunger »

moonboots wrote: post #5

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 wh…

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.

Re: Nginx 1.2.0 (stable) released

#15

Post by mattparlane »

HeroNote wrote: post #12

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

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

Re: Nginx 1.2.0 (stable) released

#16

Post by moonboots »

nilsbunger wrote: post #14
moonboots wrote: post #5

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 wh…

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.

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.

Re: Nginx 1.2.0 (stable) released

#17

Post by bostonvaulter2 »

cbsmith wrote: post #9
Jonanin wrote: post #3

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.

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

But unfortunately they are not summarized anywhere.

Re: Nginx 1.2.0 (stable) released

#18

Post by Argorak »

moonboots wrote: post #11
derefr wrote: post #7

Earlier quoted context omitted.

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

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

If you use TCP proxying, you have no way to react on HTTP headers. So either your Websocket server runs on a different port or interface or you have to proxy _all_ traffic on that port to your websocket backend.

Re: Nginx 1.2.0 (stable) released

#20

Post by nilsbunger »

moonboots wrote: post #16
nilsbunger wrote: post #14

Earlier quoted context omitted.

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.

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 B…

This isn't quite accurate. Some of these features are in the 1.0.x releases too.

Also, I think there are bugfixes (and maybe security patches?) in 1.2.x that weren't in 1.0.x.

I'm just surprised that there isn't a coalesced list of changes for going from stable->stable release.

If I was in wide production, I'd want more guidance on what changed, and when I should be upgrading.

Post reply on HN