Codeberg/Community
54
325
Fork
You've already forked Community
12

Redirection loop to the same repo #1758

Open
opened 2025年01月13日 12:54:38 +01:00 by ncts · 7 comments

Comment

Hi. I wanted to create a repo named dsum; first mistakenly under my personal account (ncts), then deleted it, and created it again under the correct organization account (nightsail). However, the resulting page https://codeberg.org/nightsail/dsum seems to have went into a strange redirection loop from/to itself:

❯ xh https://codeberg.org/nightsail/dsum
HTTP/2.0 303 See Other
content-length: 42
content-type: text/html; charset=utf-8
date: 2025年1月13日 11:48:52 GMT
location: /nightsail/dsum
(...)
<a href="/nightsail/dsum">See Other</a>.

It's possible from my account to the org account (/ncts/dsum => /nightsail/dsum), but this obviously isn't the case.

### Comment Hi. I wanted to create a repo named dsum; first mistakenly under my personal account (ncts), then deleted it, and created it again under the correct organization account (nightsail). However, the resulting page https://codeberg.org/nightsail/dsum seems to have went into a strange redirection loop from/to itself: ``` ❯ xh https://codeberg.org/nightsail/dsum HTTP/2.0 303 See Other content-length: 42 content-type: text/html; charset=utf-8 date: 2025年1月13日 11:48:52 GMT location: /nightsail/dsum (...) <a href="/nightsail/dsum">See Other</a>. ``` It's possible from my account to the org account (`/ncts/dsum` => `/nightsail/dsum`), but this obviously isn't the case.
Author
Copy link

It seems that each visit refreshes the repository to be "updated now", even though it's only a GET.

It seems that each visit refreshes the repository to be "updated now", even though it's only a GET.
ncts referenced this issue from a commit 2025年08月15日 08:02:27 +02:00
Author
Copy link

OK, today I tried to delete and recreate the repo, and when cloning it, git says

warning: remote HEAD refers to nonexistent ref, unable to checkout
OK, today I tried to delete and recreate the repo, and when cloning it, git says ``` warning: remote HEAD refers to nonexistent ref, unable to checkout ```

I observe the same behavior (303 loop) on my repo: https://codeberg.org/thiscaspar/nixos_inlet_user

But i just created the codeberg repo and then pushed my code from a local repo.

I observe the same behavior (303 loop) on my repo: https://codeberg.org/thiscaspar/nixos_inlet_user But i just created the codeberg repo and then pushed my code from a local repo.

That seems weird. But indeed, creating a repository in the place of a URL acting as a redirect breaks the said redirect.

That seems weird. But indeed, creating a repository in the place of a URL acting as a redirect breaks the said redirect.

@n0toose wrote in #1758 (comment):

That seems weird. But indeed, creating a repository in the place of a URL acting as a redirect breaks the said redirect.

But were you able to check out and use the repo eventually?

@n0toose wrote in https://codeberg.org/Codeberg/Community/issues/1758#issuecomment-7219240: > That seems weird. But indeed, creating a repository in the place of a URL acting as a redirect breaks the said redirect. But were you able to check out and use the repo eventually?

Wait, I might be misunderstanding the problem.

Wait, I might be misunderstanding the problem.

Sorry, i realize my repo is private so its not visible to others.
But even after i login in a new browser, login to codeberg, it slips into the 303 loop. Just to rule out that it's some local state issue in my browser.

I am looking for a way to make my repo actually function, and it seemed to me that you found a way to "revive it".
But of course for a functioning repo i need both the web interface on codeberg, and a functioning git server.

Your reply made me think the git server is malfunctioning after the "fix".

Sorry, i realize my repo is private so its not visible to others. But even after i login in a new browser, login to codeberg, it slips into the 303 loop. Just to rule out that it's some local state issue in my browser. I am looking for a way to make my repo actually function, and it seemed to me that you found a way to "revive it". But of course for a functioning repo i need both the web interface on codeberg, and a functioning git server. Your reply made me think the git server is malfunctioning after the "fix".
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1758
Reference in a new issue
Codeberg/Community
No description provided.
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?