It should use HTTP 2 by default. It looks like all the requests that are HTTP 1.1 from the iamdeveloper domain are being loaded by a service worker. I reckon that has something to do with it.
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I deployed my prodution and staging site on Netlify and I got reports from Lighthouse audits that some my resources are being served in HTTP/1.1 protocol which it shouldn't do that.
I found out later that all of the resurces that being served in HTTP/1.1 are from ServiceWorker. I think there's some issue with gatsby-plugin-offine
Steps to reproduce
Open DevTools with Network tab
Go to blog-staging.rayriffy.com. From this point you can see all resources are downloaded in HTTP/2 protocol
Refresh page. And you should see cached data from ServiceWorker are served in HTTP/1.1
Expected result
ServiceWorker should serve cache in HTTP/2 protocol
It should use HTTP 2 by default. It looks like all the requests that are HTTP 1.1 from the iamdeveloper domain are being loaded by a service worker. I reckon that has something to do with it.
Yeah that was what @easyaspython had guessed. So I guess a false reading from lighthouse?
It's apparently a bug with Chrome and Lighthouse.
ServiceWorker serving cache in HTTP/1.1 protocol #11123
Description
I deployed my prodution and staging site on Netlify and I got reports from Lighthouse audits that some my resources are being served in HTTP/1.1 protocol which it shouldn't do that.
I found out later that all of the resurces that being served in HTTP/1.1 are from ServiceWorker. I think there's some issue with
gatsby-plugin-offine
Steps to reproduce
Expected result
ServiceWorker should serve cache in HTTP/2 protocol
Actual result
It served in HTTP/1.1 protocol
Environment
gatsby-config.js
Source
package.json
Source
gatsby-node.js
Source
PS. I will drop repository here github.com/rayriffy/rayriffy-blog
It happens in Firefox as well. I think that bug is probably in that gatsby plugin. I've seen service workers use HTTP 2 for loading content before.