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

Option to make Riot Webclient available on matrix subdomain #324

Closed
danptr opened this issue Dec 10, 2019 · 1 comment
Closed

Option to make Riot Webclient available on matrix subdomain #324

danptr opened this issue Dec 10, 2019 · 1 comment
Labels
suggestion This issue is a feature request wontfix This issue will not be fixed by our side

Comments

@danptr
Copy link

danptr commented Dec 10, 2019

Is there an option to make the Riot Webclient available on matrix.domain.org instead of riot.domain.org. Since the default "It works! Synapse is running" isn't really needed on the matrix subdomain, port 80/443 should theoretically be available to be used by Riot, right?

@aaronraimist
Copy link
Contributor

Riot should never be run on the same domain as Synapse because it could allow for XSS attacks. element-hq/element-web#1977

@luixxiul luixxiul added wontfix This issue will not be fixed by our side suggestion This issue is a feature request labels Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion This issue is a feature request wontfix This issue will not be fixed by our side
Projects
None yet
Development

No branches or pull requests

4 participants