-
-
Notifications
You must be signed in to change notification settings - Fork 6k
Closed
Labels
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/enhancementAn improvement of existing functionalityAn improvement of existing functionality
Metadata
Metadata
Assignees
Labels
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/enhancementAn improvement of existing functionalityAn improvement of existing functionality
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
stale commentedon Sep 16, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Support HAProxy protocol
zeripath commentedon Feb 14, 2021
OK @manuelluis I have put a PR up to support this - but I think we need to be clear why Gitea needs to be aware of the proxy itself.
manuelluis commentedon Feb 14, 2021
If gitea is behind a proxy like haproxy or nginx and we like to have the original ip in the gitea logs, we can use also the
X-Forwarded-For
header if the connections are HTTP or the proxy handle the HTTPS connections.But in the case of SSH connections or if gitea handle the HTTPS and we don't break the SSL in the proxy, with the proxy protocol we can have the original ip.
zeripath commentedon Feb 14, 2021
So I think my PR does do that IIRC
Support Proxy protocol (#12527)
Support Proxy protocol (go-gitea#12527)