github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-25 16:06:45 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Chrome 136 marks /user/login?redirect_to=%2f as "Dangerous site" — does not occur in other browsers #14439

New Issue
Closed
opened 2025-11-02 11:12:59 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 11:12:59 -06:00
Owner
Copy Link

Originally created by @DimaFantasy on GitHub (May 2, 2025).

Description

Issue Summary

When accessing the login page at:
https://399221.ddns.net:3000/user/login?redirect_to=%2f
Google Chrome (Version: 136.0.7103.49, official build, 64-bit) shows a warning:

⚠️ Dangerous site — Attackers might trick you into installing software or revealing personal information such as passwords, phone numbers, or credit cards.
This behavior only occurs:

  • In Google Chrome desktop
  • On the login page only
  • With the above URL containing redirect_to=%2f
    Other pages (such as /explore, /user/repo, etc.) do not trigger the warning.
    Tested and confirmed not reproducible in:
  • Firefox (desktop)
  • Edge (desktop)
  • Chrome for Android

Notes

  • This is a test installation — the URL is temporary and may be taken down soon.
  • HTTPS and SSL certificates (Let's Encrypt) are valid and pass SSL Labs tests.
  • Cache and DNS were cleared; issue persists in incognito mode.

Question

Is it possible that the redirect_to=%2f parameter on the login URL is being flagged by Chrome's Safe Browsing?
Is there anything in Gitea's redirect logic that could be triggering this?

Browser: Google Chrome Version: 136.0.7103.49 (Official Build, 64-bit)
OS: Linux server with Gitea installed (test deployment)

Gitea Version

1.21.11

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Image

Git Version

No response

Operating System

No response

How are you running Gitea?

Gitea was installed manually using the official binary from gitea.io.
It is running as a system service via systemd on a Linux server.

Details:
Installation method: Manual (official Gitea binary)
Service manager: systemd
OS / Distro: Ubuntu 22.04 LTS
Database: SQLite (configured in /etc/gitea/app.ini)
Reverse proxy: No (accessed directly via port 3000 for testing)
HTTPS: Configured using Let's Encrypt certificate
Access URL: https://399221.ddns.net:3000/ (temporary test instance)

Database

None

Originally created by @DimaFantasy on GitHub (May 2, 2025). ### Description ### Issue Summary When accessing the login page at: [https://399221.ddns.net:3000/user/login?redirect_to=%2f](https://399221.ddns.net:3000/user/login?redirect_to=%2f) Google Chrome (Version: 136.0.7103.49, official build, 64-bit) shows a warning: > ⚠️ **Dangerous site** — Attackers might trick you into installing software or revealing personal information such as passwords, phone numbers, or credit cards. This behavior only occurs: - In **Google Chrome desktop** - On the **login page only** - With the above URL containing `redirect_to=%2f` Other pages (such as `/explore`, `/user/repo`, etc.) **do not trigger the warning**. Tested and confirmed not reproducible in: - Firefox (desktop) - Edge (desktop) - Chrome for Android --- ### Notes - This is a **test installation** — the URL is temporary and may be taken down soon. - **HTTPS and SSL certificates** (Let's Encrypt) are valid and pass SSL Labs tests. - **Cache and DNS were cleared**; issue persists in incognito mode. --- ### Question Is it possible that the `redirect_to=%2f` parameter on the login URL is being flagged by Chrome's Safe Browsing? Is there anything in Gitea's redirect logic that could be triggering this? --- **Browser:** Google Chrome Version: `136.0.7103.49` (Official Build, 64-bit) **OS:** Linux server with Gitea installed (test deployment) ### Gitea Version 1.21.11 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![Image](https://github.com/user-attachments/assets/4589cccd-4530-40ff-8a1d-2334aea6b801) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Gitea was installed manually using the official binary from [gitea.io](https://gitea.io/). It is running as a system service via systemd on a Linux server. Details: Installation method: Manual (official Gitea binary) Service manager: systemd OS / Distro: Ubuntu 22.04 LTS Database: SQLite (configured in /etc/gitea/app.ini) Reverse proxy: No (accessed directly via port 3000 for testing) HTTPS: Configured using Let's Encrypt certificate Access URL: https://399221.ddns.net:3000/ (temporary test instance) ### Database None
GiteaMirror added the issue/not-a-bug label 2025-11-02 11:12:59 -06:00
GiteaMirror commented 2025-11-02 11:13:01 -06:00
Author
Owner
Copy Link

@DimaFantasy commented on GitHub (May 2, 2025):

Update:
After my previous message, the "Dangerous site" warning in Google Chrome disappeared! The login page is now accessible without any issues.

The problem no longer occurs when visiting the login page with the same URL.

@DimaFantasy commented on GitHub (May 2, 2025): Update: After my previous message, the "Dangerous site" warning in Google Chrome disappeared! The login page is now accessible without any issues. The problem no longer occurs when visiting the login page with the same URL.
GiteaMirror commented 2025-11-02 11:13:01 -06:00
Author
Owner
Copy Link

@H0llyW00dzZ commented on GitHub (May 2, 2025):

I think it's because your domain 399221.ddns.net got flagged by Chrome, and it's not related to any bugs in this repo.

@H0llyW00dzZ commented on GitHub (May 2, 2025): I think it's because your domain `399221.ddns.net` got flagged by Chrome, and it's not related to any bugs in this repo.
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/not-a-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#14439
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?