cloudfoundry / cloudfoundry/cf-deployment
Support for HTTP/3
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 315
- Forks
- 315
- Avg merge
- 7d 9h
- Merged PRs (30d)
- 5
Description
What is this feature-request about?
In 2021, http/2 support was integrated to CF (issue). Since June 2022, http/3 is a proposed standard in RFC 9114, is supported by the major browser and offered by ~25% percent of webpages out there.
Looking at the implementation of h/2, it will probably be a cross-cutting concern with h/3 as well. Proposing to use this issue to align on plan across WGs and companies.
Please share your thoughts!
Tag your pair, your PM, and/or team!
- WG lead for App Runtime Platform: @ameowlia
- Our team is responsible for haproxy-boshrelease and willing to investigate necessary changes there (in front of gorouter)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing HTTP/2 integration referenced in issue 200 and the responsibilities of cf-deployment across Cloud Foundry working groups. Investigate the haproxy-boshrelease in front of gorouter, then document the cross-cutting plan and identify the necessary changes for HTTP/3; done means the involved teams agree on that plan.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100