Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #1584

Closed
Open
Created Sep 28, 2012 by Administrator@rootOwner

HTTP hook ignores basic auth

Created by: kirs

I have a hook to the notification script with the address: http://gitlab:[email protected], but actually the GitLab sends the hook without username/password directly to the script.domain.com.

A piece of log from nginx frontend: 10.0.3.1 - - [28/Sep/2012:08:27:38 +0000] "POST / HTTP/1.0" 401 194 "-" "-"

Is it a general issue with passing basic auth username/password via URL or there is a bug in GitLab's hook system?

Assignee
Assign to
Time tracking