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

Delete the news page "HTTP/2 Server Push in Hugo" #1540

Merged
merged 1 commit into from
Oct 12, 2021
Merged

Delete the news page "HTTP/2 Server Push in Hugo" #1540

merged 1 commit into from
Oct 12, 2021

Conversation

jmooring
Copy link
Member

See https://answers.netlify.com/t/conditional-headers-based-on-user-agent/415/16

Hey folks! Just wanted to mention that our product team has made a
decision not to ever support HTTP/2 server push, since Chrome is going
to deprecate it. We’ll focus on supporting HTTP/3 in the medium term
instead, since it will offer better performance gains.

-- Chris McCraw, Director of Support, Netlify, 17 Mar 2021

See <https://answers.netlify.com/t/conditional-headers-based-on-user-agent/415/16>

Hey folks! Just wanted to mention that our product team has made a
decision not to ever support HTTP/2 server push, since Chrome is going
to deprecate it. We’ll focus on supporting HTTP/3 in the medium term
instead, since it will offer better performance gains.

-- Chris McCraw, Director of Support, Netlify, 17 Mar 2021
@bep bep merged commit 0b7ea60 into gohugoio:master Oct 12, 2021
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

Successfully merging this pull request may close these issues.

2 participants