cors problem #26
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/gitea.com#26
Loading…
Reference in New Issue
Block a user
No description provided.
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?
chrome dev console error
Weird one,
index.js
is already loaded froms.gitea.com
, so the same-origin policy should apply.Generally, I think we'd be better to just get rid of
s.gitea.com
and serve everything fromgitea.com
, possibly offloading the/assets/
path to a static file server to take load off the Go application. With HTTP2, there is no limit on concurrent HTTP requests, so performance will be better.@silverwind Using s.gitea.com is to accelerate static assets visit via the CDN from bunny.net .
I'm sure there is a underlying bug somewhere here, but I just fail to see it yet. I don't think it can be solved with CORS as those web worker origin restrictions work differently I think.
https://stackoverflow.com/a/62914052 might be a workaround to try.
I will try that later.
Since I have moved s.gitea.com back to gitea.com, this could be closed.