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

REQUIRE_SIGNIN_VIEW when true migrate fails with 403 #7089

New Issue
Closed
opened 2025-11-02 07:15:34 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 07:15:34 -06:00
Owner
Copy Link

Originally created by @basaran on GitHub (Mar 30, 2021).

  • Gitea version (or commit ref):
    Gitea version 1.13.6 built with GNU Make 4.1, go1.15.10 : bindata, sqlite, sqlite_unlock_notify

  • Database (use [x]):

    • SQLite

  • Can you reproduce the bug at https://try.gitea.io:

    • Yes (provide example URL)
    • No

  • Log gist:

2021/03/30 12:31:54 Started GET / for 127.0.0.1
2021/03/30 12:31:54 Completed GET / 200 OK in 180.201023ms
2021/03/30 12:31:58 Started GET /api/v1/version for 127.0.0.1
2021/03/30 12:31:58 Completed GET /api/v1/version 403 Forbidden in 966.575µs
2021/03/30 12:32:03 Started GET /api/v1/version for 127.0.0.1
2021/03/30 12:32:03 Completed GET /api/v1/version 403 Forbidden in 820.394µs

Description

When REQUIRE_SIGNIN_VIEW is enabled to true, migration from another gitea source fails with 403 forbidden.

Screenshots

image

image

Originally created by @basaran on GitHub (Mar 30, 2021). - Gitea version (or commit ref): Gitea version 1.13.6 built with GNU Make 4.1, go1.15.10 : bindata, sqlite, sqlite_unlock_notify - Database (use `[x]`): - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - Log gist: 2021/03/30 12:31:54 Started GET / for 127.0.0.1 2021/03/30 12:31:54 Completed GET / 200 OK in 180.201023ms 2021/03/30 12:31:58 Started GET /api/v1/version for 127.0.0.1 2021/03/30 12:31:58 Completed GET /api/v1/version 403 Forbidden in 966.575µs 2021/03/30 12:32:03 Started GET /api/v1/version for 127.0.0.1 2021/03/30 12:32:03 Completed GET /api/v1/version 403 Forbidden in 820.394µs ## Description When REQUIRE_SIGNIN_VIEW is enabled to `true`, migration from another gitea source fails with 403 forbidden. ## Screenshots ![image](https://user-images.githubusercontent.com/30809170/113023862-19bc8e00-9154-11eb-9523-3f558f2e7164.png) ![image](https://user-images.githubusercontent.com/30809170/113023986-3b1d7a00-9154-11eb-95b0-1b7a780126aa.png)
GiteaMirror added the topic/repo-migrationissue/needs-feedback labels 2025-11-02 07:15:34 -06:00
GiteaMirror commented 2025-11-02 07:15:35 -06:00
Author
Owner
Copy Link

@noerw commented on GitHub (Apr 1, 2021):

I can't reproduce, the problem must be elsewhere.
The log you provided is unrelated.

@noerw commented on GitHub (Apr 1, 2021): I can't reproduce, the problem must be elsewhere. The log you provided is unrelated.
GiteaMirror commented 2025-11-02 07:15:35 -06:00
Author
Owner
Copy Link

@basaran commented on GitHub (Apr 1, 2021):

REQUIRE_SIGNIN_VIEW was the only parameter I changed to get the gitea to gitea migration working. I tested on different repositories too. When it is set to true, it will return 403. But I will setup two new test instances this weekend and report back.

@basaran commented on GitHub (Apr 1, 2021): REQUIRE_SIGNIN_VIEW was the only parameter I changed to get the gitea to gitea migration working. I tested on different repositories too. When it is set to `true`, it will return 403. But I will setup two new test instances this weekend and report back.
GiteaMirror commented 2025-11-02 07:15:36 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 8, 2021):

Which side did you changed the config? Send side Gitea or receive side Gitea?

@lunny commented on GitHub (Apr 8, 2021): Which side did you changed the config? Send side Gitea or receive side Gitea?
GiteaMirror commented 2025-11-02 07:15:36 -06:00
Author
Owner
Copy Link

@basaran commented on GitHub (Apr 8, 2021):

REQUIRE_SIGNIN_VIEW was set to true on the gitea where repository was cloned from (acting as source server). I haven't had the time last week, but I will do two clean installs this weekend to replicate the issue.

@basaran commented on GitHub (Apr 8, 2021): REQUIRE_SIGNIN_VIEW was set to true on the gitea where repository was cloned from (acting as source server). I haven't had the time last week, but I will do two clean installs this weekend to replicate the issue.
GiteaMirror commented 2025-11-02 07:15:36 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 23, 2021):

Were you able to reproduce?

@zeripath commented on GitHub (Jun 23, 2021): Were you able to reproduce?
GiteaMirror commented 2025-11-02 07:15:36 -06:00
Author
Owner
Copy Link

@basaran commented on GitHub (Jun 23, 2021):

Hi, I completely forgot about this. Sorry about that. I will setup the test vms this weekend, and let you know.

@basaran commented on GitHub (Jun 23, 2021): Hi, I completely forgot about this. Sorry about that. I will setup the test vms this weekend, and let you know.
GiteaMirror commented 2025-11-02 07:15:36 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 28, 2021):

closing as presumed fixed

@zeripath commented on GitHub (Oct 28, 2021): closing as presumed fixed
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 issue/needs-feedback topic/repo-migration
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#7089
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?