You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2021. It is now read-only.
I found a strange behaviour while handling CONNECT requests when authentication is enabled. If the client does not provide credentials the connection is just simply closed instead of responding with 401 and demanding (basic) authentication as it happens with regular proxy req's.
The text was updated successfully, but these errors were encountered:
zsoltm
changed the title
Tunneling with auth enabled
Dropping "CONNECT" connections instead of 401 when auth is required
Aug 5, 2016
zsoltm
changed the title
Dropping "CONNECT" connections instead of 401 when auth is required
Dropping "CONNECT" request instead of 401 when auth is required
Aug 5, 2016
I found a strange behaviour while handling CONNECT requests when authentication is enabled. If the client does not provide credentials the connection is just simply closed instead of responding with 401 and demanding (basic) authentication as it happens with regular proxy req's.
Could be tested easily:
... whereas:
Non-tunneling requests does it correctly:
The text was updated successfully, but these errors were encountered: