| Issue 587469 | Remove SPDY/3.1 | ||||||||||||||||||||||||||||||||||||||||
| Starred by 5 users | Project Member Reported by davidben@chromium.org, Feb 17 2016 | Back to list | |||||||||||||||||||||||||||||||||||||||
Sign in to add a comment
|
(See http://www.chromium.org/blink#launch-process for an overview) bnc: Had you filed one of these already? I couldn't find it. Feel free to merge and update the chromestatus.com entry if you have. Change description: SPDY/3.1 is the experimental application layer protocol that provides performance improvements over HTTP/1.1 by, for example, connection multiplexing and server push. SPDY/3.1 is superseded by HTTP/2, which was published as an RFC last May. Changes to API surface: We will no longer negotiate SPDY/3.1 over HTTPS connections. Sites using it will return to negotiating HTTP/1.1 (unless they upgrade to HTTP/2) at a performance hit, but no loss in functionality. Links: Public standards discussion: https://tools.ietf.org/html/rfc7540 Support in other browsers: Internet Explorer: Firefox: Safari: *Make sure to fill in any labels with a -?, including all OSes this change affects. Feel free to leave other labels at the defaults.
Comment 1
by
davidben@chromium.org,
Feb 17 2016
,
May 2 2016
According to https://www.chromestatus.com/feature/5711167683035136 SPDY/3.1 support was removed in Chromium 50. Is that correct? I’m still seeing `quic/1+spdy/3` usage for https://ssl.google-analytics.com/ga.js in DevTools → Network using Chrome 52 Canary.
,
May 2 2016
Re #3: sorry, that is incorrect. SPDY/3.1 was removed from Chromium 51, at https://crrev.com/1869783004. 'quic/1+spdy/3' in fact is not SPDY/3.1, but another procotol, QUIC. The value of that string is a historical artifact.
,
May 2 2016
Thanks for clarifying. I guess the same goes for NPN, then (https://www.chromestatus.com/feature/5767920709795840). I’ve updated the ChromeStatus entries and submitted a patch to update the blog post at https://developers.google.com/web/updates/2016/03/chrome-50-deprecations (https://github.com/google/WebFundamentals/pull/2875). Should the `+spdy/3` part be removed from the string?
,
May 2 2016
Yes, same goes for NPN. Thank you for updating the Chrome Status entries. I agree that changing that string would be nice. However, it might interact badly with metrics, persisted preferences, and other moving parts, so unfortunately it is far from trivial, and thus not high priority.
,
Jun 28 2016
,
Jul 11 2016
SPDY/3.1 functionality is disabled, concluding this launch bug. Issue 624095 tracks further effort to clean up SPDY/3.1-related, now dead, code. |
||||||||||||||||||||||||||||||||||||||||
| ► Sign in to add a comment | |||||||||||||||||||||||||||||||||||||||||