Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !132

Merged
Created Jan 26, 2017 by iv@ivContributor

gitlab: use trusted proxies mechanism

  • Overview 3
  • Commits 2
  • Changes 5

If not using trusted proxies, our frontend IPv6 are banned because rack attacks thinks the clients of the lab are the frontends, and banned them after a few mistakes on credentials, making the lab inaccessible for everyone.

Let's use X-Forwarding-For HTTP header set by the frontend to see the real client IPs. For this, it is necessary to add real_ip module to nginx.

Also, if this MR is accepted, I will need the IPv6 of the real lab frontends to set them as instance parameter nginx_real_ip_trusted_addresses.

More details on issue 9.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: trusted-proxies
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7