Skip to content

Fix reverse proxy pattern #103

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

Merged
merged 5 commits into from
Mar 24, 2020
Merged

Fix reverse proxy pattern #103

merged 5 commits into from
Mar 24, 2020

Conversation

avara1986
Copy link
Member

@avara1986 avara1986 commented Mar 23, 2020

Create a Proxy pattern https://microservices.io/patterns/apigateway.html.
You can run the microservice A in your local machine in http://localhost:5000/my-endpoint/

If you deploy your microservice, in some cases, this microservice runs behind a cluster, a gateway... and this gateway redirect traffic to the microservice with a specific path like yourdomian.com/my-ms-a/my-endpoint/.

This fix understands this path if the gateway send a specific header:

@avara1986 avara1986 added the Improvement Not a bug but... could be better label Mar 23, 2020
@coveralls
Copy link

coveralls commented Mar 23, 2020

Coverage Status

Coverage decreased (-0.06%) to 99.177% when pulling d9c2ab6 on fix/reverse_proxy_pattern into 517e5b6 on master.

@avara1986 avara1986 merged commit 266411c into master Mar 24, 2020
@avara1986 avara1986 deleted the fix/reverse_proxy_pattern branch March 24, 2020 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Not a bug but... could be better
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants