Vercel should of course serve everything through HTTP/2, however I notice that it’s all HTTP/1.1
My site is a NextJS (latest version) build served through Vercel on a Hobby account, using a *.vercel.app domain.
Any ideas?
Vercel should of course serve everything through HTTP/2, however I notice that it’s all HTTP/1.1
My site is a NextJS (latest version) build served through Vercel on a Hobby account, using a *.vercel.app domain.
Any ideas?
Hi @kylewetton, welcome to the Vercel Community!
I can confirm that the projects I’ve hosted on Vercel are using h2, so I’d be curious why it’s not working for you. I’ve tested both custom domains and vercel.app
domains.
Can you share the link to your website?
Interesting to note that I have another site under an Enterprise account that serves mostly 1.1 as well
Hi @kylewetton, thanks for sharing additional information.
For me your website is serving on h2
, maybe it is with your browser? Can you share which browser version and OS are you using?
Ah interesting! Here’s my user agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36
Currently checking in Chrome
This is from Auckland, New Zealand
Hi @kylewetton, this is interesting. Can you try updating the Google Chrome to the latest version?
In the meantime, let me talk to other folks internally.
Okay so I checked on my personal computer and it was h2
all the way down. The only differences between that computer and the one I’m seeing the 1.1
on, is that the latter has Netskope who use middleman certs, I wonder if it’s relaying the network calls to me through some kind of “security edge” thing that’s causing this.
It’s an interesting observation but I think I know enough now to not pursue any kind of resolve at least.
Oh, I see. Thanks for sharing your findings here.