7 ms·
Nginx 1.2.0 (stable) released
- AncientPC 15y agoChangelog: http://nginx.org/en/CHANGES-1.2 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 15y agoI 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.
- mattparlane 15y agoThey 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 15y agoCompared to the 1.0.x branch, there are a lot of new features.
- bostonvaulter2 15y agoBut unfortunately they are not summarized anywhere.
- njharman 15y agohere http://news.ycombinator.org/item?id=3882617 http://news.ycombinator.org/item?id=3882617
- moonboots 15y agoIn 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 15y agoInteresting--does the above-mentioned feature mean that nginx can finally be put in front of a websocket server (e.g., socket.io)?
- AUmrysh 15y agoI 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 15y agoThis is fantastic, I was just talking about this on HN a few days ago: http://news.ycombinator.com/reply?id=3865966&whence=threads%3fid%3dpippy http://news.ycombinator.com/reply?id=3865966&whence=thre...
- moonboots 15y agoI'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 https://github.com/yaoweibin/nginx_tcp_proxy_module
- Argorak 15y agoIf 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.
- patrickaljord 15y agoIn 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 http://trac.nginx.org/nginx/milestone/1.3.0
- mdesantis 15y agoas WebSockets too
- HeroNote 15y agoFree Nginx ebook update: http://www.heronote.com/files/nginx.htm http://www.heronote.com/files/nginx.htm
- mh- 15y agono PDF?
- mattparlane 15y agoThat 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 15y agoThat 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.