How to configure as a forward proxy that handles https?

134 views
Skip to first unread message

Drew Thompson

unread,
Apr 16, 2024, 1:31:29 PM4/16/24
to envoy-users
I cannot get envoy to match * routes for https the same way I can easily get it to match for http.  

I can get HTML replies to BOTH these requests in squid but not envoy.  Envoy returns a 404
curl  http://www.google.com --proxy http://fwd-proxy:10000
curl  https://www.google.com --proxy http://fwd-proxy:10000

According to  https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/http/http_routing

HTTP routing

Envoy includes an HTTP router filter which can be installed to perform advanced routing tasks.

...

Envoy also has the ability to be configured as forward proxy. In the forward proxy configuration, mesh clients can participate by appropriately configuring their HTTP proxy to be an Envoy.

I, like this user started from the dynamic forward proxy example config and also receive 404 no route found for https requests.   The suggestion to use SNI did not get me anywhere as the examples in the sandbox are doing something completely different than what I'm attempting and the documentation states SNI is in alpha and not production ready either.  

Any configuration help with actual yaml would be greatly appreciated.  The configuration I started from is here https://www.envoyproxy.io/docs/envoy/v1.29.3/configuration/http/http_filters/dynamic_forward_proxy_filter.html#dynamic-forward-proxy

Thanks,
Drew



Reply all
Reply to author
Forward
0 new messages