Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why set both Authorization and Proxy-Authorization headers? #36

Open
StephenWakely opened this issue Jun 1, 2023 · 0 comments
Open

Why set both Authorization and Proxy-Authorization headers? #36

StephenWakely opened this issue Jun 1, 2023 · 0 comments

Comments

@StephenWakely
Copy link

StephenWakely commented Jun 1, 2023 •
edited
Loading

In set_authorization if the intercept is not http or https, it sets both Authorization and Proxy-Authorization headers.

It's not clear to me why this should be the case and strikes me as a bug. It's not clear to me why we would need to set different headers according to the scheme of the intercept at all. I'm not finding any relevant information in the RFC.

Do you have any ideas? Thanks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@StephenWakely