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

The https connection should not be closed if there is no proxy-authorization header #264

Open
Dgofre opened this issue Mar 21, 2023 · 0 comments
Open

The https connection should not be closed if there is no proxy-authorization header #264

Dgofre opened this issue Mar 21, 2023 · 0 comments

Comments

@Dgofre
Copy link

Dgofre commented Mar 21, 2023

The https connection should not be closed if there is no proxy-authorization header because the client sends the first CONNECT request without a proxy-authorization header, then receives the status code 407 in response and only then sends the CONNECT request together with the proxy-authorization header.
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
@Dgofre