1

In late 2017, Twitter announced and implemented improvements to support HTTP/2. Adopting new protocols means ending support for old protocols. Among those old protocols is SPDY, a networking protocol whose deprecation was announced in 2015 as the new standard, HTTP/2, was ratified.

Sometime after Jan 15, 2020, all connections to the Twitter API (and all other Twitter domains) will no longer support SPDY connections. This change will affect all formats and tiers of the API (REST, streaming, and webhooks; standard, premium, enterprise, and Ads and Media APIs), as well as the wider Twitter platform.

What should I do now?

We recommend reviewing all code that connects to the Twitter API, and validating that it uses libraries that supports modern networking protocols. Specifically, you must ensure that if your code currently negotiates a SPDY connection to api.twitter.com and associated domains, that it instead negotiates a HTTP/1.1 or HTTP/2 connection. Please note, that by default, most connections fallback to HTTP/1.1, if SPDY is not supported, and likely no action will be required. However, you should confirm this behavior in your code.

2 Likes