basic auth when unwrapping comment in PR #5214

Closed
opened 2025-11-02 06:18:07 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @browcio on GitHub (Apr 9, 2020).

Description

Steps to reproduce:

  1. Create new repo with long file
  2. Change something in that file and create PR
  3. Create single comment in code diff
  4. In conversation view press up arrow in code block
  5. basic auth pops up

Looks like gitea do not allow user to access /OWNER/REPO/blob_excerpt/.

Originally created by @browcio on GitHub (Apr 9, 2020). - Gitea version (or commit ref): 1.12.0+dev-126-g743022116 - Can you reproduce the bug at https://try.gitea.io: - [X] Yes (provide example URL): https://try.gitea.io/ppiwowa2/testrepo/pulls/3 - [ ] No - [ ] Not relevant ## Description Steps to reproduce: 1. Create new repo with long file 2. Change something in that file and create PR 3. Create single comment in code diff 4. In conversation view press up arrow in code block 5. basic auth pops up Looks like gitea do not allow user to access /OWNER/REPO/blob_excerpt/.
GiteaMirror added the issue/staletype/bug labels 2025-11-02 06:18:07 -06:00
Author
Owner

@guillep2k commented on GitHub (Apr 10, 2020):

Please make your try.gitea.io repository public so we can access it.

@guillep2k commented on GitHub (Apr 10, 2020): Please make your `try.gitea.io` repository public so we can access it.
Author
Owner

@stale[bot] commented on GitHub (Jun 9, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jun 9, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Jun 23, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 23, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Author
Owner

@browcio commented on GitHub (Aug 18, 2020):

Sorry for delay. I made this repo public. Problem still persists.

@browcio commented on GitHub (Aug 18, 2020): Sorry for delay. I made this repo public. Problem still persists.
Author
Owner

@lunny commented on GitHub (Aug 18, 2020):

Did you? The arrows on the conversation have been removed.

@lunny commented on GitHub (Aug 18, 2020): Did you? The arrows on the conversation have been removed.
Author
Owner

@browcio commented on GitHub (Aug 18, 2020):

Strange. I really believe that I confirmed that before posting. Nevertheless we found similar issue in 1.12.3 but I cannot reproduce it on 1.13-dev so we will wait.

Thank you.

@browcio commented on GitHub (Aug 18, 2020): Strange. I really believe that I confirmed that before posting. Nevertheless we found similar issue in 1.12.3 but I cannot reproduce it on 1.13-dev so we will wait. Thank you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5214