Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #8616

Closed
Open
Created 10 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

project import: HTTP scheme with unsupported registry part not handled

Closed

project import: HTTP scheme with unsupported registry part not handled

Created by: paulmenzel

Creating a new project and, in the Import existing git repo field, entering an URL in HTTP scheme and with a registry part (by for example taking an URL in SSH scheme without removing the colon :) an internal server error triggered and the user sees a 500 error page.

    Completed 500 Internal Server Error in 31ms

    ActionView::Template::Error (the scheme http does not accept registry part: username:password@gitlab.com:company (or bad hostname?)):
        4:       %h2
        5:         %i.fa.fa-spinner.fa-spin
        6:         Import in progress.
        7:       %p.monospace git clone --bare #{hidden_pass_url(@project.import_url)}
        8:       %p Please wait while we import the repository for you. Refresh at will.
        9:       :javascript
       10:         new ProjectImport();
      app/helpers/projects_helper.rb:278:in `hidden_pass_url'
      app/views/projects/import.html.haml:7:in `_app_views_projects_import_html_haml__597848005956285849_69818793815300'

It’d be great, if an error message could be shown to the user.

Linked issues
0


  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: paulmenzel

    This is with GitLab 7.5.2.

    By Administrator on 2015-01-20T10:55:27 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
Assign to
Milestone
No milestone
None
None
Time tracking
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
participants
Reference:

Menu

Projects Groups Snippets
Help