Skip to content

[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

Merged

Conversation

bagasme
Copy link
Contributor

@bagasme bagasme commented Dec 25, 2019

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.

@codecov-io
Copy link

Codecov Report

Merging #9491 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
models/unit.go 62.16% <0%> (-5.41%) ⬇️
services/pull/temp_repo.go 31.62% <0%> (-2.57%) ⬇️
models/webhook.go 69.39% <0%> (-1.07%) ⬇️
modules/log/event.go 64.61% <0%> (-1.03%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b2f29c...1c8d4d9. Read the comment docs.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Dec 25, 2019
@bagasme
Copy link
Contributor Author

bagasme commented Dec 25, 2019

Codecov report seems weird, as only updating docs can decrease coverage only slightly on supposedly random files?

@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Dec 25, 2019
@lafriks lafriks added the type/docs This PR mainly updates/creates documentation label Dec 25, 2019
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Dec 26, 2019
@lunny
Copy link
Member

lunny commented Dec 26, 2019

@bagasme Please note @mrsdizzie's comment.

@lunny
Copy link
Member

lunny commented Dec 26, 2019

make L-G-T-M work

@lunny lunny merged commit 114d474 into go-gitea:master Dec 26, 2019
@mrsdizzie
Copy link
Member

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.

@bagasme
Copy link
Contributor Author

bagasme commented Dec 26, 2019

@mrsdizzie Feel free to open new PR with your suggestions.

@bagasme bagasme deleted the docs/https-reverse-termination-proxy-note branch December 26, 2019 05:59
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Docs] Clarify TLS Termination Proxy
7 participants