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

[Proposal] Allow GET routes on API without CSRF #7071

New Issue
Closed
opened 2025-11-02 07:15:04 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:15:04 -06:00
Owner
Copy Link

Originally created by @kasbah on GitHub (Mar 25, 2021).

Gitea has some GET requests that make changes and thus these are protected with CSRF (see e.g. https://github.com/go-gitea/gitea/issues/4838). I don't think any API GET requests make changes though so can we open this up to be queried without needing a csrf token?

This would allow for easier querying of the API from e.g. /api/swagger and other web pages served from the same domain as Gitea.

Originally created by @kasbah on GitHub (Mar 25, 2021). Gitea has some GET requests that make changes and thus these are protected with CSRF (see e.g. https://github.com/go-gitea/gitea/issues/4838). I don't think any API GET requests make changes though so can we open this up to be queried without needing a csrf token? This would allow for easier querying of the API from e.g. /api/swagger and other web pages served from the same domain as Gitea.
GiteaMirror commented 2025-11-02 07:15:05 -06:00
Author
Owner
Copy Link

@kasbah commented on GitHub (Mar 28, 2021):

I noticed now that you can do some GET requests e.g. /user/search. The one I was wondering about is actually GET /user for the currently logged in user and there is probably a reason for needing csrf on that one.

@kasbah commented on GitHub (Mar 28, 2021): I noticed now that you can do _some_ GET requests e.g. `/user/search`. The one I was wondering about is actually GET `/user` for the currently logged in user and there is probably a reason for needing csrf on that one.
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
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#7071
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?