Google dumps SPDY in favour of HTTP/2, any plans for nginx?
mat999 at gmail.com
Sat Feb 14 14:35:42 UTC 2015
Indeed. The Wikipedia page covers it quite well FYI -
So what is really being asked is for a roadmap for the implementation of
the non-draft differences (i.e HTTP/2.0 allows for non TLS communication,
and multiplexes differently). I am sure nginx will once again be at the
forefront of technology and implement it when possible. :)
On Wed, Feb 11, 2015 at 11:38 AM, Ilya Grigorik <igrigorik at gmail.com> wrote:
> Pedantic, but I object to the wording in the title :) ... SPDY was/is an
> experimental branch of HTTP/2, and now that HTTP/2 is in the final stages
> of becoming a standard, there is no longer the need for SPDY and hence the
> announcement of a deprecation timeline -- it's not and never was SPDY vs.
> HTTP/2. That aside...
> From what I understand (at least from a few conversations at nginx.conf),
> there is already some existing efforts around enabling http/2 support? I'd
> love to see some official product plans and/or timelines as well.
> On Tue, Feb 10, 2015 at 3:25 PM, mex <nginx-forum at nginx.us> wrote:
>> Google dumps SPDY in favour of HTTP/2, any plans ore roadmap for HTTP/2 in
>> "HTTP is the fundamental networking protocol that powers the web. The
>> majority of sites use version 1.1 of HTTP, which was defined in 1999 with
>> RFC2616. A lot has changed on the web since then, and a new version of the
>> protocol named HTTP/2 is well on the road to standardization. We plan to
>> gradually roll out support for HTTP/2 in Chrome 40 in the upcoming weeks.
>> HTTP/2’s primary changes from HTTP/1.1 focus on improved performance. Some
>> key features such as multiplexing, header compression, prioritization and
>> protocol negotiation evolved from work done in an earlier open, but
>> non-standard protocol named SPDY. Chrome has supported SPDY since Chrome
>> but since most of the benefits are present in HTTP/2, it’s time to say
>> goodbye. We plan to remove support for SPDY in early 2016, and to also
>> remove support for the TLS extension named NPN in favor of ALPN in Chrome
>> the same time. Server developers are strongly encouraged to move to HTTP/2
>> and ALPN."
>> Posted at Nginx Forum:
>> nginx mailing list
>> nginx at nginx.org
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx