Nginx 1.2.0 (stable) released • Hacker News Board

Re: Nginx 1.2.0 (stable) released

#21

Post by moonboots » Tue, Apr 24, 2012, 8:04 AM UTC

nilsbunger wrote: post #20

moonboots wrote: post #16

Earlier quoted context omitted.

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.

You're right; it looks like a few of these features like the max range directive were also included in 1.0.

Bug fixes and security patches are applied to both stable and dev branches. Some of the recent buffer overflow patches only affect features added in 1.1.

Hopefully future changelogs can be more comprehensive and usable now that nginx has venture funding.

Re: Nginx 1.2.0 (stable) released

#22

Post by mrweasel » Tue, Apr 24, 2012, 9:04 AM UTC

mattparlane wrote: post #15

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

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.

Re: Nginx 1.2.0 (stable) released

#23

Post by mdesantis » Tue, Apr 24, 2012, 9:11 AM UTC

patrickaljord wrote: post #6

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

as WebSockets too

Re: Nginx 1.2.0 (stable) released

#24

Post by pornel » Tue, Apr 24, 2012, 10:33 AM UTC

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

WebSockets aren't HTTP — fake header is not enough to fool HTTP-compliant servers/proxies. You could try HTTPS WebSockets with TLS 1.1 SNI vhosts.

I recommend using Server-Sent Events instead. You get nearly same API for realtime server->client push, and they're HTTP-compatible:

http://html5doctor.com/server-sent-events/ http://speakerdeck.com/u/pornel/p/server-sent-events