github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Repeatedly hitting Sign In button results in evergrowing redirect_to chain #8018

New Issue
Closed
opened 2025-11-02 07:51:08 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 07:51:08 -06:00
Owner
Copy Link

Originally created by @laurivosandi on GitHub (Oct 24, 2021).

Gitea Version

1.15.5

Git Version

Docker image

Operating System

Not applicable

How are you running Gitea?

Docker image

Database

MySQL

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Description

Repeatedly hitting Sign In button results in ever increasing chain for redirect_to GET argument leading to eventual error 500.

I guess this is done to preserve GET arguments for other views but for /user/login this does not make sense.

Looking at my Gitea server logs looks like some web crawlers get stuck in these loops.

Screenshots

No response

Originally created by @laurivosandi on GitHub (Oct 24, 2021). ### Gitea Version 1.15.5 ### Git Version Docker image ### Operating System Not applicable ### How are you running Gitea? Docker image ### Database MySQL ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Description Repeatedly hitting Sign In button results in ever increasing chain for `redirect_to` GET argument leading to eventual error 500. I guess this is done to preserve GET arguments for other views but for `/user/login` this does not make sense. Looking at my Gitea server logs looks like some web crawlers get stuck in these loops. ### Screenshots _No response_
GiteaMirror added the type/bug label 2025-11-02 07:51:08 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8018
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?