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

Support CORS headers to http receive-pack/send-pack like gogs #2741

New Issue
Closed
opened 2025-11-02 04:46:16 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 04:46:16 -06:00
Owner
Copy Link

Originally created by @abhishiv on GitHub (Jan 11, 2019).

  • Gitea version (or commit ref): 1.5.0

Description

Hello, I would like to propose adding Access-Control-Allow-Origin header flag to gitea.

I'm in terested in this in order to get @isomorphic-git/isomorphic-git working with gitea in the browser. Gogs already supports it.

[http]
ACCESS_CONTROL_ALLOW_ORIGIN = *

...

Further background

cc: @wmhilton

Originally created by @abhishiv on GitHub (Jan 11, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.5.0 ## Description Hello, I would like to propose adding `Access-Control-Allow-Origin` header flag to gitea. I'm in terested in this in order to get [@isomorphic-git/isomorphic-git](https://github.com/isomorphic-git/isomorphic-git) working with gitea in the browser. Gogs [already](https://isomorphic-git.org/blog/2018/04/07/gogs-adds-cors-headers-for-isomorphic-git.html) supports it. ``` [http] ACCESS_CONTROL_ALLOW_ORIGIN = * ``` ... Further [background](https://github.com/isomorphic-git/isomorphic-git#cors-support) cc: @wmhilton
GiteaMirror added the type/enhancement label 2025-11-02 04:46:16 -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/enhancement
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#2741
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?