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

Client -> nginx reverse proxy -> external forward proxy -> target service possible? #211

Closed
BenjaminDaSilva opened this issue Feb 10, 2022 · 1 comment

Comments

@BenjaminDaSilva
Copy link

Hi there,

I found some kind of similar questions (166, 210) but in details my scenario is different:

I have a client C (part of a web application) which can't be configured to use a forward proxy for API calls to a service S that can only be reached via a forward proxy F. This web app though runs on a virtual appliance which runs nginx to reverse proxy inbound connections to the web app.

Could I enable this nginx with this module to act as reverse proxy R but not pass_proxy directly to service S but via the forward proxy F?

So basically:

[ C ] ---- API Call ----> [ R ] ----- CONNECT / tunnel ----> [ F ] -----> [ S ]

@BenjaminDaSilva BenjaminDaSilva changed the title Client -> ngingx reverse proxy -> external forward proxy -> target service possible? Client -> nginx reverse proxy -> external forward proxy -> target service possible? Feb 10, 2022
@chobits
Copy link
Owner

chobits commented Mar 26, 2022

This is technically feasible. But this module does not support this feature.

It needs a new nginx upstream module to fire CONNECT tunnel request to upstream and then proxy data flow via this tunnel to backend.

According to my nginx-C developing experience, it is hard to modify and debug nginx upstream from its C core base.

@chobits chobits closed this as completed Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants