-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[HELP!!!] Can envoy be configured to use a second http/https proxy #34136
Comments
@alyssawilk probably understands this. |
Envoy can both forward CONNECT request, encapsulate traffic in CONNECT and terminate CONNECT. |
@alyssawilk I want to achieve is that all http/https in this pod must go through my clash client proxy service before accessing the target website. , so I want to use EnvoyFilter to achieve it, but I really understand too little about this. For example, I want to intercept all http/https export traffic of the pod labeled app, and forward this part of the traffic to my clash client proxy server (assuming the address is http://a.b.c.com:40001, supporting HTTP over connect ), but I am a complete novice on envoy-related knowledge. Can you help show me how to implement the code? I will be very grateful~~~ |
The following is what I learned from some information I searched before:
But it doesn't work. I don't quite understand how to modify it, even though I checked a lot of information. |
@alyssawilk could you help me~ 0.0 |
apologies, but I think you're going to have to play around - I'm unfortunately too overloaded to dig in the way I'd need to to help out. |
OK, Thanks. |
Title: Can envoy be configured to use a second http/https proxy
Description:
I am using envoy as an edge proxy. There is a use case where the whole network is behind an http proxy(support HTTP over connect). Is there a way to have envoy redirect to this second proxy?
i.e. client(http/https,xxx.com)->envoy->[http proxy2]->xxx.com
Does envoy honor the HTTP_PROXY/HTTPS_PROXY/NO_PROXY environment variables? Is there another way?
The text was updated successfully, but these errors were encountered: