microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
Add support for using HTTP/2 & possibly HTTP/3 as well instead of only HTTP/1.1
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe the problem.
AFAICT, the GraphServiceClient uses HTTP/1.1 & there's no chance of instructing it to use HTTP/2 (or even HTTP/3) instead - at least not without rewriting basically half of the client.
Describe the solution you'd like.
Please allow configuration of the HTTP version used, preferably by providing an optional argument that's passed down to the HttpClientHandler's HttpVersion & defaulting to HTTP/1.1.
Additional context?
No response
Contributor guide
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
Locate the GraphServiceClient entry point and trace how its HttpClientHandler is created and configured. Determine how an optional HTTP version setting could preserve the HTTP/1.1 default while allowing HTTP/2, and clarify whether HTTP/3 is in scope. Done means the client exposes the requested configuration without requiring callers to rewrite its setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100