Javascript error: same origin policy #29080
Labels
Comments
|
It looks like you embedded something strange (not the same origin) into the page.
|
Lol, that should only be a grafical bug of bitwaden. But will test it with disabled bitwarden. |
Could you help to provide the embedded HTML (bitwarden or something else)? Then we can make Gitea ignore these non-same origin resources, then there will be no error anymore. |
|
You were correct, it is Bitwarden, still strange that it only happens in firefox (and not in chrome), they are probably more strict.
how can I do that? |
|
Could you also try to figure out the outer ps: I proposed a fix #29081. |
that doesn't seem right |
|
was not able to copy it directly |
when ready I could test it with a rootless docker image |
We can't do builds for pull requests, so you'd have to build from source and run that. What are the minimal steps to reproduce? Just install the Bitwarden extension and open Gitea? Any specific settings made in the extension? |
it has to firefox, but I think that's all, |
|
Odd, because I'm also a Bitwarden user on Firefox and have never seen this error. There must be something different about your setup. |
|
|
|
My extension does not have this "Show auto-fill menu on form fields" option, maybe that is causing the iframe? Try toggling it off. What's the version of your extension? Mine is 2024.1.1. 
|
mine too |
|
As per this the feature is only enabled for Bitwarden Cloud users, which I'm not 😆. |
|
I like bitwarden, but decisions like that, I just cannot understand. Should I create a test Bitwarden account and send the credentials to you? |
techknowlogick
changed the title
|
No, it's fine. #29081 will fix it, one way or another. |
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Feb 8, 2024
…erent origin on the page (go-gitea#29081) Try to fix go-gitea#29080
wxiaoguang
added a commit
that referenced
this issue
Feb 8, 2024
…erent origin on the page (#29081) (#29089) Backport #29081 by wxiaoguang Try to fix #29080 Co-authored-by: wxiaoguang <[email protected]>
Will set up a new docker shortly |
|
with the nightly docker it works perfectly how long is the release cycle for the stable (latest) version? |
|
It's not a fixed cycle, but I would expect 1.21.6 in around maybe 1-2 weeks. |
|
nice, |
silverwind
pushed a commit
to silverwind/gitea
that referenced
this issue
Feb 20, 2024
…erent origin on the page (go-gitea#29081) Try to fix go-gitea#29080
silverwind
added a commit
that referenced
this issue
Feb 22, 2024
So we don't get issues like #29080 and #29273 any more. Only active in [production builds](https://webpack.js.org/guides/production/#specify-the-mode), in non-production the errors will still show.
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Feb 22, 2024
So we don't get issues like go-gitea#29080 and go-gitea#29273 any more. Only active in [production builds](https://webpack.js.org/guides/production/#specify-the-mode), in non-production the errors will still show.
silverwind
added a commit
that referenced
this issue
Feb 22, 2024
Backport #29303 by @silverwind So we don't get issues like #29080 and #29273 any more. Only active in [production builds](https://webpack.js.org/guides/production/#specify-the-mode), in non-production the errors will still show. Co-authored-by: silverwind <[email protected]>
6543
pushed a commit
to 6543-forks/gitea
that referenced
this issue
Feb 26, 2024
…ith different origin on the page (go-gitea#29081) Try to fix go-gitea#29080 (cherry picked from commit f290c24)
DennisRasey
pushed a commit
to DennisRasey/forgejo
that referenced
this issue
Feb 27, 2024
So we don't get issues like go-gitea/gitea#29080 and go-gitea/gitea#29273 any more. Only active in [production builds](https://webpack.js.org/guides/production/#specify-the-mode), in non-production the errors will still show. (cherry picked from commit 532da5ed5ee3edb45d2ee63c6ab0fad53473691f)
|
Automatically locked because of our CONTRIBUTING guidelines |
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this issue
Jan 23, 2025
…erent origin on the page (go-gitea#29081) (go-gitea#29089) Backport go-gitea#29081 by wxiaoguang Try to fix go-gitea#29080 Co-authored-by: wxiaoguang <[email protected]> (cherry picked from commit 9a4d283)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I get an error from my browser that Gitea tried to access forbidden elements to to SOP
Gitea Version
1.21.1 (-rootless)
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
portainer stack
Database
SQLite
The text was updated successfully, but these errors were encountered: