Skip to content
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

Upstream HTTP/1 server through authenticated (SQUID) proxy #15116

Closed
jeratora opened this issue Feb 19, 2021 · 3 comments
Closed

Upstream HTTP/1 server through authenticated (SQUID) proxy #15116

jeratora opened this issue Feb 19, 2021 · 3 comments
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@jeratora
Copy link

jeratora commented Feb 19, 2021

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

@jeratora jeratora added the triage Issue requires triage label Feb 19, 2021
@junr03 junr03 added question Questions that are neither investigations, bugs, nor enhancements and removed triage Issue requires triage labels Feb 19, 2021
@cortex93
Copy link

cortex93 commented Mar 5, 2021

@jeratora you will find a sample at #11308 (comment)

@github-actions
Copy link

github-actions bot commented Apr 4, 2021

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.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Apr 4, 2021
@github-actions
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

3 participants