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
When accessing an URI via proxy, the client should use "GET" for HTTP-Targets and CONNECT for HTTPS-Targets.
Actual Behavior
The Client always uses CONNECT. This is technical valid but breaks things like proxy-side request filtering for Non-HTTP requests.
Steps to Reproduce
Create a client with http proxy set to localhost:someport. Run netcat (nc -l -p someport). Query a http url through that client. Check what request is issued.
Expected Behavior
When accessing an URI via proxy, the client should use "GET" for HTTP-Targets and CONNECT for HTTPS-Targets.
Actual Behavior
The Client always uses CONNECT. This is technical valid but breaks things like proxy-side request filtering for Non-HTTP requests.
Steps to Reproduce
Create a client with http proxy set to localhost:someport. Run netcat (nc -l -p someport). Query a http url through that client. Check what request is issued.
Your Environment
The text was updated successfully, but these errors were encountered: