Skip to content
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

fix(main): filter out frame-ancestors if exists in Content-Security-Policy #938

Merged
merged 1 commit into from
Jan 3, 2024

Conversation

emrahcom
Copy link
Contributor

@emrahcom emrahcom commented Jan 3, 2024

The application filters out frame-ancestors if it exists in content-security-policy but it doesn't check Content-Security-Policy (with uppercase for the first letter) which is the recommend style in most guides.

In our use-case, we integrate Jitsi with our Keycloak server as identity provider and it uses Content-Security-Policy. So, it doesn't work if the application doesn't have this update.

@saghul saghul merged commit c81e79c into jitsi:master Jan 3, 2024
3 checks passed
@emrahcom emrahcom deleted the fix-content-security-policy branch January 3, 2024 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants