HTTP2 or HTTP3 for Pages

[cqueern]

Select Topic Area

Product Feedback

Body

Would it be possible for Pages to be delivered by HTTP2 or HTTP3? I'm currently seeing HTTP1.1. Thanks!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Akkii88]

GitHub Pages does support HTTP/2, but not HTTP/3 yet. Here's what you need to know:

HTTP/2 Support

GitHub Pages automatically serves content over HTTP/2 when HTTPS is enabled and enforced. If you're seeing HTTP/1.1, it's likely because:

1. HTTPS is not enforced - Go to your repository Settings → Pages and check the "Enforce HTTPS" option
2. Custom domain TLS certificate pending - If you recently added a custom domain, GitHub needs time to provision the certificate (usually a few minutes)
3. DNS misconfiguration - Ensure your DNS records point to the correct GitHub Pages IPs

To verify HTTP/2 is working:

• Open DevTools (F12) → Network tab
• Right-click the column headers and enable Protocol
• Reload your page - you should see h2 in the Protocol column

HTTP/3 Support

GitHub Pages does not currently support HTTP/3 (QUIC). While the main github.com site has started rolling out HTTP/3, this hasn't been extended to the Pages hosting infrastructure yet. There's an ongoing discussion about HTTP/3 support if you'd like to follow updates.

Reference

The official announcement about HTTPS and HTTP/2 support for custom domains was made in this GitHub blog post.