Tell HN: Cloudflare has started rolling out HTTP/2 support

#1

Post by someguy1233 » Tue, Dec 01, 2015, 7:59 PM UTC

Check your own sites. Some bigger sites like HN haven't got it, but most of my smaller ones have suddenly gotten the blue HTTP/2 lightning bolt out of nowhere. I'm not on any of their paid plans, just the normal free plan.

Note: The CEO said the rollout would happen this week on twitter https://twitter.com/eastdakota/status/670703144276365312

Re: Tell HN: Cloudflare has started rolling out HTTP/2 support

#2

Post by someguy1233 » Tue, Dec 01, 2015, 8:01 PM UTC

Update: looks like I might have caught them in their testing phase. One of my sites has suddenly been downgraded back to SPDY, but one of the other sites is still HTTP/2

Re: Tell HN: Cloudflare has started rolling out HTTP/2 support

#3

Post by [deleted] » Tue, Dec 01, 2015, 8:15 PM UTC

someguy1233 wrote: post #2

Update: looks like I might have caught them in their testing phase. One of my sites has suddenly been downgraded back to SPDY, but one of the other sites is still HTTP/2

[deleted]

Re: Tell HN: Cloudflare has started rolling out HTTP/2 support

#4

Post by someguy1233 » Tue, Dec 01, 2015, 8:24 PM UTC

[deleted] wrote: post #3

someguy1233 wrote: post #2

Update: looks like I might have caught them in their testing phase. One of my sites has suddenly been downgraded back to SPDY, but one of the other sites is still HTTP/2

[deleted]

Aha, correct. Loaded up the website that appeared downgraded, it's still HTTP/2 in the incognito window, and chrome://net-internals/#http2 does confirm that it is in-fact real HTTP/2 (not the extension being odd).

Why would this behaviour happen? I don't understand why it does the initial session in HTTP/2 but then drops to SPDY upon further requests

Re: Tell HN: Cloudflare has started rolling out HTTP/2 support

#5

Post by [deleted] » Tue, Dec 01, 2015, 8:27 PM UTC

someguy1233 wrote: post #4

[deleted] wrote: post #3

Earlier quoted context omitted.

[deleted]

Aha, correct. Loaded up the website that appeared downgraded, it's still HTTP/2 in the incognito window, and chrome://net-internals/#http2 does confirm that it is in-fact real HTTP/2 (not the extension being odd). Why would this behaviour happen? I don't understand why it does the initial session in HTTP/2 but then drops to SPDY upon further requests

[deleted]