-
Notifications
You must be signed in to change notification settings - Fork 493
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.
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
Unable to restrict the domain name of forward proxy #230
Comments
It is as expected that proxied data cannot be restricted via domain name. Note that we have no method to parse the proxied data in CONNECT tunnel. Many people have asked why or how to parse, hijack, and intercept proxy data. This is practically impossible to achieve. |
The only data you can parse is the CONNECT request before the CONNECT tunnel is established. You can check this request as following( note that I dont test the script, just for reference.
|
restrict domain example
|
Think it resolved. Feel free to reopen it if you still have same issue. |
0. Before Your ASK
Ⅰ. Issue Description
Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
Proxies can be restricted normally
Ⅳ. How to reproduce it (as minimally and precisely as possible)
V. Anything else we need to know?
None
VI. Environment:
Nginx 1.19.2
The text was updated successfully, but these errors were encountered: