github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-22 05:15:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

add HTTP authentication for webinterface #14776

New Issue
Open
opened 2025-11-02 11:22:42 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 11:22:42 -06:00
Owner
Copy Link

Originally created by @milahu on GitHub (Jul 18, 2025).

Feature Description

some gitea instances require login to explore repos

it would be nice to store the login data in a bookmark
like https://someuser:somepassword@example.com/

https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Authentication

RFC 7235 defines the HTTP authentication framework, which can be used by a server to challenge a client request, and by a client to provide authentication information.

similar but different:
HTTP authentication for API #24160

this feature would conflict with "require captcha for login"

Screenshots

No response

Originally created by @milahu on GitHub (Jul 18, 2025). ### Feature Description some gitea instances require login to explore repos it would be nice to store the login data in a bookmark like `https://someuser:somepassword@example.com/` https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Authentication > [RFC 7235](https://datatracker.ietf.org/doc/html/rfc7235) defines the HTTP authentication framework, which can be used by a server to [challenge](https://developer.mozilla.org/en-US/docs/Glossary/Challenge) a client request, and by a client to provide authentication information. similar but different: HTTP authentication for API #24160 this feature would conflict with "require captcha for login" ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 11:22:42 -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/proposal
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#14776
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?