alex / alex/what-happens-when

SPDY is depreciated

Open
#228 2 comments 9 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
43.3k
Forks
5.7k
PR merge metrics
No merged PRs in 30d

Description

According to Wikipedia and various development blogs, support for SPDY is being removed from browsers and NGINX has removed support as HTTP/2 has many of the same features. I suggest mention of SPDY be replaced with HTTP/2 as that is the new standard and it has superseded SPDY.

The section in which SPDY is mentioned is in the HTTP protocol section. This could be a good time to expand upon the section with going into detail if HTTP/2 becomes the selected protocol during communication.

"In February 2015, Google has announced that following the recent final ratification of the HTTP/2 standard, support for SPDY would be deprecated, and that support for SPDY would be withdrawn.[7] Google removed SPDY support in Google Chrome 51. Mozilla removed it in Firefox 50."

https://en.wikipedia.org/wiki/SPDY

"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 6, but since most of the benefits are present in HTTP/2, it’s time to say goodbye. "

https://blog.chromium.org/2015/02/hello-http2-goodbye-spdy.html

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.