-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Piped instance has modified CORS #1
Comments
Hey Kavin, Which changes do you suggest doing in order to improve it? 😊 |
I see, would've made an issue there had I known, apologies! I would suggest removing these two lines: https://github.com/garuda-linux/infrastructure-nix/blob/05f1858efcca44880d42eca0d4b60d105b7a37f4/nix/web-dragon.nix#L62-L63 This would allow any website to use your API/backend, which is essential for allowing any frontend to use it! See https://github.com/TeamPiped/Piped#made-with-piped for an idea of other frontends that could use it :) It also breaks the instance switcher in https://piped.video/preferences, which is also an issue! Thanks! |
You also seem to have another issue, where you have two |
Interesting, I'm taking a look at this too. |
I had to change it to:
in order to allow video play on the web interface. While Libretube worked flawlessly, I noticed videos were not playing on the page. The console reported the removed header as missing. Would this still be fine for the use cases you mentioned? @FireMasterK |
You could actually remove those lines too since the proxy actually adds those headers now! (The old one in Golang didn't) You still have a duplicate Thanks for fixing the issues! |
Hi there,
Not sure if this is the right place to make issues regarding services.
Could the
access-control-allow-origin
header please not be modified on the API/backend? It prevents other frontends to Piped's API from using it.Thanks in advance!
The text was updated successfully, but these errors were encountered: