-
-
Notifications
You must be signed in to change notification settings - Fork 575
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
Hi team, request help for accessing proxyee. #290
Comments
I know what you mean, but unfortunately proxyee not support transparent mode currently, it only follow standard HTTP proxy. |
Thanks, if I want to add code to support transparent mode? Shall I get some suggestions of how to do? |
Transparent mode has no handshake step, so I think the packet should be entry here directly, you can add a transparent flag on Looking forward to the results of your test, and can contribute to the project if it works! |
Thanks a lot! I suddenly found an error in my description. I'm sure I need use VPC route and iptables PREROUTING to redirect traffic to proxyee. Next, I do need forward request to 3rd parties' proxy which is in public net. In this way, is |
Yes, that's right. |
In my mind, there are two VPS A and B in same VPC, then I will add a top route rule for this VPC 0.0.0.0/0 -> B. This means all the traffic from VPS A will be lead to B. And I will start a proxyee service in VPS B. Also, I will config iptables on VPS B by command below:
Then all the traffic from VPS A will go through netty proxyee. I have already installed the certificate on VPS A.
I hope to use this way to hide proxy to client.
I tried two ways by sending request from VPS A.
First:
curl -x proxyeeIp:port https://www.google.com
. In this way, everything works well, with-v
option, I can see the certificate is using correctly. But it needs me explicitly config proxy.Second:
curl https://www.google.com
. In this way, this traffic will be lead to proxyee based on route table and iptables configuraiton, but I will got error like below:Sometimes the error message is
netty exception about invalid version format
.I tried to debug and I found the invalid message comes from
io.netty.handler.codec.http.HttpObjectDecoder.splitInitialLine(ByteBuf asciiBuffer)
. I check this method's responsibility by debugging theFirst way
. This method will format bytes to string which will contains uri, http method and etc.I don't understand why this error happens on
Second way
. If it's related to SSL certificate, the first way shouldn't success.Could someone help? Thanks a lot!
The text was updated successfully, but these errors were encountered: