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

New option to support upstream self signed ssl connections #24

Closed
jc21 opened this issue Nov 4, 2018 · 4 comments
Closed

New option to support upstream self signed ssl connections #24

jc21 opened this issue Nov 4, 2018 · 4 comments

Comments

@jc21
Copy link
Member

jc21 commented Nov 4, 2018

Some upstream hosts only provide a SSL connection and they are sometimes using self signed certificates (EdgeOS is one such example).

Would be nice to have an option to specify that the upstream is SSL and the nginx proxy would ignore certificate errors because the server should be in control of the user who's creating the reverse proxy.

In most cases this means that the Proxy Host setup requires SSL as well and the added benefit here is that the edge host will be using a certified certificate at all times, regardless of what the upstream host has.

@sh4444dow
Copy link

That feature is definetely needed in a bunch of situations. I even considered to produce a pull request concerning this feature. Did you start to implement it ?

Sincerely,

@sh4444dow

@jc21
Copy link
Member Author

jc21 commented Dec 12, 2018

No not yet. I left this note for myself to get to later. Give me a couple of days and I'll see if I have time to put it in quickly.

@sh4444dow
Copy link

Okay =) If I'm not mistaken, this enhancement note is strongly related to #34 issue. I link it just for reminder.

Sincerely,

@sh4444dow

@jc21
Copy link
Member Author

jc21 commented Jan 3, 2019

Added in v2.0.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants