giacomochiarella opened a new issue, #24785:
URL: https://github.com/apache/superset/issues/24785
A clear and concise description of what the bug is.
#### How to reproduce the bug
We have such config in superset_config.py
```
HTTP_HEADERS = {
"X-Frame-Options": "ALLOW-FROM *",
"x-frame-options": "ALLOW-FROM *",
"Content-Security-Policy": "frame-ancestors http://* https://*";,
"content-security-policy": "frame-ancestors http://* https://*";
}
DEFAULT_HTTP_HEADERS = {
"X-Frame-Options": "ALLOW-FROM *",
"x-frame-options": "ALLOW-FROM *",
"Content-Security-Policy": "frame-ancestors http://* https://*";,
"content-security-policy": "frame-ancestors http://* https://*";
}
OVERRIDE_HTTP_HEADERS = {
"X-Frame-Options": "ALLOW-FROM *",
"x-frame-options": "ALLOW-FROM *",
"Content-Security-Policy": "frame-ancestors http://* https://*";,
"content-security-policy": "frame-ancestors http://* https://*";
}
```
but once a dashboard is embedded in an iframe, the client keeps getting
x-frame-options: SOMEORIGIN
### Expected results
I was expecting to override x-frame-options header
### Actual results
The client keeps receiving x-frame-options: SOMEORIGIN
what is the right way to remove this limitation?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
