-
Notifications
You must be signed in to change notification settings - Fork 813
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
[bug] Not able to use filestash inside iframe #537
Comments
Iframe is blocked by default because it would open your instance to clickjacking attacks. That's the reason this exists: |
When I use domain with port it is working. But when I use ip with the port I get dead screen with cat. |
Also login is not working (not Authorised) once I add domains. It doesn't matter if I try within iframe or direct url, as soon as iframe property is filed, login stop working. |
Any idea what could be wrong? Do you have enough information for testing? |
Is this planned to be fixed in near future? |
Any news? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Description of the bug
Tried to include it in Home assistant but getting error.
Refused to frame because an ancestor violates the following Content Security Policy directive: "frame-ancestors.
Step by step instructions to reproduce the bug
Simply try to use it in any iframe html element.
Can you replicate that error from the demo?
Cannot be tested as demo is working over https, that is a different behaviour and problem.
Observed behavior
Framing filestash in iframe should be allowed in my opinion.
The text was updated successfully, but these errors were encountered: