Skip to content
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

Watch: "Intent to Remove: HTTP/2 and gQUIC server push" #11

Open
ocean90 opened this issue Apr 16, 2021 · 1 comment
Open

Watch: "Intent to Remove: HTTP/2 and gQUIC server push" #11

ocean90 opened this issue Apr 16, 2021 · 1 comment

Comments

@ocean90
Copy link
Member

ocean90 commented Apr 16, 2021

See https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ.

Current status (11.03.2021, 22:51:50):

Our conclusion is that while we are in general supportive of removing HTTP/2 push for the reasons given, we'd like support to be removed only once there is an Early Hints implementation that can be tested in the wild. While Early Hints is not solving exactly the same problem, its motivation is similar and therefore sites may be able to obtain similar performance to HTTP/2 push with that feature. Waiting for this will allow sites to potentially switch to Early Hints and not lose overall performance.

@ocean90
Copy link
Member Author

ocean90 commented Aug 18, 2022

https://twitter.com/patmeenan/status/1559943970481913856

👀 HTTP/2 PUSH is finally going away in Chrome 106: https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/ho4qP49oAwAJ

HTTP 103 is the best way to early-hint out-of-band.

Thanks to the community and teams that made this possible (standards teams for 103, CDNs for implementing, Net team, huge effort)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant