HTTP 307 Redirect: Authentication information is not forwared
- Dominant language
- TypeScript
- Stars
- 40k
- Forks
- 2.4k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
### Expected Behavior
We call a REST URL via HTTP GET with the Authorization: Bearer header. As a response we get an HTTP 307 redirect to a different page. We would expect that all headers including the Authorization: Bearer header are forwarded to the new URL and that the correct response from the new URL is returned
### Actual Behavior
The actual behavior is that the redirect to the new URL is performed and all headers except the Authorization: Bearer header are forwarded. However, as the new page is requiring authentication in the same way as the original URL, the call fails with an HTTP 401 error.
### Reproduction Steps
The API is not public - therefore I cannot describe how somebody else could reproduce the issue.
### Is there an existing issue for this?
- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.
### Additional Information
_No response_
### Insomnia Version
2023.4.0
### What operating system are you using?
macOS
### Operating System Version
Ventura 13.4.1
### Installation method
Downloaded from the Insomnia page
### Last Known Working Insomnia version
_No response_
Contributor guide
Research direction
The issue names no source files, tests, or entry points. Start by locating the HTTP 307 redirect handling and testing an authenticated request that redirects; done means the redirected request preserves the expected authentication behavior and no longer fails with HTTP 401.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100