-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[Docs] Clarify HTTPS Termination Proxy on Using Reverse Proxy to Enable HTTPS #9491
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
[Docs] Clarify HTTPS Termination Proxy on Using Reverse Proxy to Enable HTTPS #9491
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9491 +/- ##
==========================================
- Coverage 41.53% 41.52% -0.02%
==========================================
Files 572 572
Lines 74752 74752
==========================================
- Hits 31051 31041 -10
- Misses 39850 39863 +13
+ Partials 3851 3848 -3
Continue to review full report at Codecov.
|
Codecov report seems weird, as only updating docs can decrease coverage only slightly on supposedly random files? |
@bagasme Please note @mrsdizzie's comment. |
…xy-note' into docs/https-reverse-termination-proxy-note
make L-G-T-M work |
It looks like my suggestion wasn't applied from Github but just some of it was retyped. There are still some typos and missing words. |
@mrsdizzie Feel free to open new PR with your suggestions. |
Indeed, enabling HTTPS by reverse proxy often called TLS Termination Proxy. It is optional to also combine it with enabling HTTPS with internal server in case of public instances.
This will close #9354.