-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
get ssl error #600
Comments
There are so many middle services so it's hard to follow. In goproxy, http mitm and https MITM are separated. |
`
` |
This comment was marked as outdated.
This comment was marked as outdated.
If this problem happens only when using this project, I would analyze what it does and log the information about every single request. |
thats my new code ,https req is ok,but http req failed ,how to resolve it |
As mentioned above, I use the tun2proxy library to forward all traffic to goproxy, but goproxy doesn't seem to be able to distinguish between http/https requests and processes them all as https. This error occurs. Can you tell me how to configure it to handle it correctly? |
I may have found the problem. tun2proxy is a VPN that will establish a connect tunnel between proxy servers to forward all traffic. So goproxy receives only connect requests, which leads to misjudgment and treats http as https. |
Yes, this is what I told you in the last message. If you use TLS for HTTP, obviously it doesn't work... |
2024/12/25 15:11:20 [007] INFO: on 0th handler: &{2 0x1220e00} 47.243.34.160:80
2024/12/25 15:11:20 [007] INFO: Assuming CONNECT is TLS, mitm proxying it
2024/12/25 15:11:20 [007] INFO: signing for 47.243.34.160
2024/12/25 15:11:20 [007] WARN: Cannot handshake client 47.243.34.160:80 tls: first record does not look like a TLS handshake
data stream=> android vpnservice->tun2proxy->goproxy
error forward http request to https request
how to fix it
The text was updated successfully, but these errors were encountered: