-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bubblewrap fails on sites that use HTTP/2 #516
Comments
Hey @JudahGabriel In the stacktrace above, we can see Here's the output of Expand to see the output:
|
Adding a bit more context here. node-fetch, they underlying library for requests, doesn't support HTTP/2 (see node-fetch/node-fetch#342). Generally, this shouldn't be a big issue since, as a best practice, servers should be configured to do HTTP/2 Upgrade instead of HTTP/2 only, as many clients don't support it yet. I see the server in questions is currently configured to do upgrades:
|
Interesting. So this is a combination of using HTTP/2 (node-fetch doesn't yet support it) and the web server blocking access? If the web server is blocking access, why can the browser access it from the same IP? |
From my |
Closed via #522 and published in v1.13.2. |
When generating a TWA for a site that uses HTTP/2, Bubblewrap fails with the following error:
Steps to reproduce the behavior:
Run Bubblewrap on a site that serves HTTP/2 content, such as https://jued.ru. This can be done from PWABuilder as well. You'll receive the above error.
I think the underlying issue is that Bubblewrap uses node-fetch, and node-fetch doesn't support HTTP/2. We've had several bugs opened on PWABuilder where the user gets the above error when creating a TWA package. Upon investigation, the issue is the site is using HTTP/2. Original bug report here.
Most of the times we see this error, it's because the developer enabled Cloudflare, which allows HTTP/2 (and HTTP/3!) with the flip of a switch.
The text was updated successfully, but these errors were encountered: