Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar

Do not update/delete: Banner broadcast message test data

Do not update/delete: Notification broadcast message test data

  • Muhammad Dewji
  • GitLabGitLab
  • Repository
Switch branch/tag
  • gitlab
  • spec
  • lib
  • gitlab
  • ci
  • yaml_processor_spec.rb
Find file BlameHistoryPermalink
  • Douwe Maan's avatar
    Protect Gitlab::HTTP against DNS rebinding attack · a9bcddee
    Douwe Maan authored Apr 21, 2019 and Oswaldo Ferreir's avatar Oswaldo Ferreir committed May 30, 2019
    Gitlab::HTTP now resolves the hostname only once, verifies the IP is not
    blocked, and then uses the same IP to perform the actual request, while
    passing the original hostname in the `Host` header and SSL SNI field.
    a9bcddee