ps. REMEMBER you need openssl 1.0.1 - previous versions will not work with spdy and distributions like CentOS do not come with the newer version. You can switch to the IUS repo in that case http://iuscommunity.org/pages/Repos.html
Re:Nginx-1.3.15 development version released, featuring expe...
by muxxa on Tuesday March 26, 2013 @02:06PM
(#5445017)
I tripped up on the NPN module when building openssl from source - great tip with the yum replacement installation. Note: you also need to have EPEL installed for the above to work:
Re:Nginx-1.3.15 development version released, featuring expe...
by ck2 on Wednesday March 27, 2013 @12:22AM
(#5447773)
Ah I may have had epel enabled already, I think Centos6 even comes with the repo file, you just have to edit to enable it. If not, they run their own mirror so you don't even need to specify one.
Re:Nginx-1.3.15 development version released, featuring expe...
by hobohacker on Thursday March 28, 2013 @01:17AM
(#5453423)
Can you clarify this statement? Perhaps there's missing context, but as it reads, it seems like a false statement. When I look at chrome://view-http-cache/, I see a bunch of https:// resources for google.com (which are served over SPDY).
Re:Nginx-1.3.15 development version released, featuring expe...
by josteink on Tuesday March 26, 2013 @03:50PM
(#5445654)
How real is this interest for Google's non-standard anyway?
Is anyone going to switch their production setup to run software in development merely to support a "internet-protocol" entirely controlled by a single company known for developing things behind closed doors?
SPDY on the open internet makes no fucking sense.
This is Microsoft and MSIE all over again, but people are evidently too blinded by Google-fandom to realize it.
Re:Nginx-1.3.15 development version released, featuring expe...
by kyrra on Tuesday March 26, 2013 @04:43PM
(#5445949)
The HTTP 2.0 draft is using SPDY as a starting point for "asynchronous connection multiplexing, header compression, and request-response pipelining, while maintaining full backwards compatibility with the transaction semantics of HTTP 1.1"
So while Google may have come up with SPDY, we may get it as part of HTTP 2.0, from a standards organization. So it's not totally in Google's hands. It's being used as a starting point for a standard.
Re:Nginx-1.3.15 development version released, featuring expe...
by maratd on Tuesday March 26, 2013 @05:08PM
(#5446089)
> we may get it
Which I think is the key statement here. This is all fantastic work, from both Google and those working on the draft, but this is years from being standardized properly and years more before it's ubiquitous on all browsers.
Also, while its performance is very impressive when comparing against vanilla HTTPS, I haven't seen any impressive numbers of it vs vanilla HTTP?
Re:Nginx-1.3.15 development version released, featuring expe...
by coldtea on Tuesday March 26, 2013 @05:39PM
(#5446243)
>This is all fantastic work, from both Google and those working on the draft, but this is years from being standardized properly and years more before it's ubiquitous on all browsers.
Just like CSS3 and HTML5. But you can start using it now, all the same, and many people do, all the same.
>Also, while its performance is very impressive when comparing against vanilla HTTPS, I haven't seen any impressive numbers of it vs vanilla HTTP?
It's not supposed to be used with HTTP. And the web of the future is not supposed to have much HTTP without S, either.
Re:Nginx-1.3.15 development version released, featuring expe...
by ProblemFactory on Tuesday March 26, 2013 @07:03PM
(#5446627)
As far as I understand, it's not necessary to wait until SPDY is ubiquitous on all browsers. By enabling SPDY support in Nginx and setting one header in HTTP responses, you can serve your content via both protocols. Any SPDY-enabled visitors would discover the feature, and switch after the first HTTP request.
On the browser side, Chrome supports SPDY, and has market share of somewhere between 25-50%.
So if I'm not mistaken, enabling this module would make things faster for a large fraction of your visitors, while being backwards-compatible with any browser.
Patch was very stable, no problems and spdy just works.
Apparently work on the patch/module was sponsored by Automattic (WordPress, Matt Mullenweg) so thanks to them and whomever worked on it! Some background here https://barry.wordpress.com/2012/06/16/nginx-spdy-and-automa...
ps. REMEMBER you need openssl 1.0.1 - previous versions will not work with spdy and distributions like CentOS do not come with the newer version. You can switch to the IUS repo in that case http://iuscommunity.org/pages/Repos.html
Processing of requests from SPDY connections cannot be rate limited."
http://nginx.org/en/docs/http/ngx_http_spdy_module.html
Note to all: This is a development branch release.
Is anyone going to switch their production setup to run software in development merely to support a "internet-protocol" entirely controlled by a single company known for developing things behind closed doors?
SPDY on the open internet makes no fucking sense.
This is Microsoft and MSIE all over again, but people are evidently too blinded by Google-fandom to realize it.
So while Google may have come up with SPDY, we may get it as part of HTTP 2.0, from a standards organization. So it's not totally in Google's hands. It's being used as a starting point for a standard.
http://datatracker.ietf.org/doc/draft-ietf-httpbis-http2/
http://en.wikipedia.org/wiki/HTTP_2.0
Which I think is the key statement here. This is all fantastic work, from both Google and those working on the draft, but this is years from being standardized properly and years more before it's ubiquitous on all browsers.
Also, while its performance is very impressive when comparing against vanilla HTTPS, I haven't seen any impressive numbers of it vs vanilla HTTP?
Just like CSS3 and HTML5. But you can start using it now, all the same, and many people do, all the same.
>Also, while its performance is very impressive when comparing against vanilla HTTPS, I haven't seen any impressive numbers of it vs vanilla HTTP?
It's not supposed to be used with HTTP. And the web of the future is not supposed to have much HTTP without S, either.
On the browser side, Chrome supports SPDY, and has market share of somewhere between 25-50%.
So if I'm not mistaken, enabling this module would make things faster for a large fraction of your visitors, while being backwards-compatible with any browser.