You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Is it possible to configure Envoy so that an incoming request is forwarded to an upstream server through an corporate proxy requiring authentication ? (credentials being set in Envoy).
The pipeline would look like this : client --> sidecar Envoy (TLS origination + proxy credentials) --> Corporate Squid Proxy --> upstream server (REST)
I was thinking about using CONNECT but I'm not sure about HTTP1/1 complete support. As a fallback, a direct response + a LUA script using OpenRESTY to make proxied calls to the upstream server. But to be honest, I would prefer a pure "proxy" solution.
Thanks in advance for any hint / pointer / sample configuration.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
Description:
Is it possible to configure Envoy so that an incoming request is forwarded to an upstream server through an corporate proxy requiring authentication ? (credentials being set in Envoy).
The pipeline would look like this : client --> sidecar Envoy (TLS origination + proxy credentials) --> Corporate Squid Proxy --> upstream server (REST)
I was thinking about using CONNECT but I'm not sure about HTTP1/1 complete support. As a fallback, a direct response + a LUA script using OpenRESTY to make proxied calls to the upstream server. But to be honest, I would prefer a pure "proxy" solution.
Thanks in advance for any hint / pointer / sample configuration.
Relevant Links:
#11308
The text was updated successfully, but these errors were encountered: