microsoft / microsoft/libHttpClient
Redirects should not pass along the authorization header for security and usability reasons
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 295
- Forks
- 144
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Apple does this by default (see https://github.com/Alamofire/Alamofire/issues/798) but it appears the Windows http implementation give flexibility here. To be consistent across platforms as well not leak auth tokens to other locations, the auth header should be removed.
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
Start by tracing redirect handling in the Windows HTTP implementation and compare it with Apple's default behavior, using the linked Alamofire issue as context. Confirm how authorization headers are carried across redirects, then ensure redirected requests do not pass the authorization header to other locations and verify platform-consistent behavior with the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100