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

Turning off HTTPs in API-Umbrella #296

Closed
djphan opened this issue Sep 29, 2016 · 1 comment
Closed

Turning off HTTPs in API-Umbrella #296

djphan opened this issue Sep 29, 2016 · 1 comment
Milestone

Comments

@djphan
Copy link

djphan commented Sep 29, 2016

Hi,

Just curious with this doc on HTTPs configs: http://api-umbrella.readthedocs.io/en/latest/server/https-config.html and this old issue chain: #112

It was mentioned that for:

SSL Termination: If you’re placing API Umbrella behind a load balancer in a multi-server setup, you can handle the SSL termination with that external load balancer

I was wondering if there was a way to turn off HTTPs/SSL checking in the .yml file. I have a similar setup with a load balancer in front of API-Umbrella where I'd like to handle SSL termination there. But it is unclear to the details on how you're doing so there when the default API-Umbrella has its own self signed certificates.

Thanks

@GUI GUI added this to the v0.14.0 milestone Feb 21, 2017
@GUI
Copy link
Member

GUI commented Feb 23, 2017

Sorry for the delay. We've added some additional documentation about SSL termination in a couple places:

https://api-umbrella.readthedocs.io/en/latest/server/https-config.html
https://api-umbrella.readthedocs.io/en/latest/server/listen-ports.html

Generally speaking, you should be able to perform SSL termination, and things should just work as long as your SSL terminator sends back X-Fowarded-Proto and X-Forwarded-Port headers. I know Amazon ELBs do this by default, and we use ELBs for SSL termination in some of our uses. But let us know if that doesn't answer your question, or you're still having any issues.

@GUI GUI closed this as completed Feb 23, 2017
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