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
  • #6358

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

  • Report abuse

  • New issue

  • Report abuse

Redirect loop after testing service settings

Closed

Redirect loop after testing service settings

Created by: heikobornholdt

When I open the edit page for GitLab CI-Service of a GitLab Project (http://example.com/foo/bar/services/gitlab_ci/edit), click to "Test settings", wait for page to refresh and click "Test settings" again, it will result in a "redirect loop".

I believe, the redirect_to :back instruction (https://github.com/gitlabhq/gitlabhq/blob/2ed7cbfba4ff3c6a4cf3e72515a0375544998de0/app/controllers/projects/services_controller.rb#L31) causes this problem.

Now I have dozens of pending builds on my GitLab CI 😆

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: IgnoredAmbience

      Initially browse to /edit, after the first click we navigate to /test, which is 302 redirected to /edit. This does not update the browser's address bar, so the next click on the button originates from /test, to which we're 302 redirected.

      By Administrator on 2014-11-11T18:56:24 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: IgnoredAmbience

      This bug doesn't seem to be quite as simple as it first seems. In Firefox 32.0.3 I've reloaded the page and it is now working as expected (was failing earlier). However in Chromium 37.0.2062.120 I'm still seeing the failure.

      By Administrator on 2014-11-11T21:38:41 (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