Discussion in 'Server Configuration and Hosting' started by Andy.N, Feb 4, 2014.
Great news for those using nginx over https
No update from dotdeb. I guess I should wait...
Really important because the next version of Chrome and Firefox are removing support for SPDY 2. Meaning if you don't upgrade Nginx, users will lose SPDY support.
You guys using nginx repository or compile it by yourself?
Self-compile for us.
Source compile. Took me less than 2 minutes to update to Nginx 1.5.10 with Centmin Mod - just hit menu option 4 and enter 1.5.10 when prompted
Using centminmod turned out to be a pretty smart move by us
have you ever running any testing to see how your site performs on SPDY 2/3 vs without SPDY?
Yeah... It sucks without SPDY once you are used to it being enabled all the time.
easy if you have IE10 browser, just load your SPDY enabled site via IE10 and you will see how non-SPDY performance is
Just updated myself. Again, nice and easy with Centmin
There's little reason not to compile Nginx yourself. Many distros add modules which increase your binary size. Cutting out the fat and being able to load non-default modules to run the most optimized binary possible is a good thing. Nginx is small and very quick to compile even on modest hardware.
Upgraded to SPDY 3.1 today... and for some reason the Server Push stuff doesn't seem to be working... hmmm... maybe that didn't make it into Nginx.
So "Mainline" is stable enough for production test?
Another user of CentMin Mod here
Also upgraded mine to nginx 1.5.10 and Spdy 3.1
Thanks for the heads up!
Yeah, I haven't had any issues with it. If you check out the changelog between stable and mainline you get a list of bug fixes that looks worth the risk. I'd run mainline then switch to stable if you have problems. It's easy enough to switch Nginx versions with zero downtime. See the documentation for the steps to do it: http://wiki.nginx.org/CommandLine#Upgrading_To_a_New_Binary_On_The_Fly
for those running SPDY on a Centminmod install, did you have any issues initially with CSS not displaying correctly on Chrome but working on other browsers? tracking down a bizarre issue after enabling SSL/TLS+SPDY where CSS just wont render at all in Chrome.
I don't have any css problem's on mine.
Are you using ngx_pagespeed?
Separate names with a comma.