matrix-docker-ansible-deploy/roles/matrix-server
Slavi Pantaleev 9dad4c7c2d Fix /.well-known/matrix/client for CORS
This is provoked by Github issue #46.

No client had made use of the well-known mechanism
so far, so the set up performed by this playbook was not tested
and turned out to be a little deficient.

Even though /.well-known/matrix/client is usually requested with a
simple request (no preflight), it's still considered cross-origin
and [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)
applies. Thus, the file always needs to be served with the appropriate
`Access-Control-Allow-Origin` header.

Github issue #46 attempts to fix it at the "reverse-proxying" layer,
which may work, but would need to be done for every server.
It's better if it's done "upstream", so that all reverse-proxy
configurations can benefit.
2018-11-29 09:13:25 +02:00
..
defaults Rename variable (matrix_synapse_ext_password_provider_ldap -> matrix_synapse_ext_password_provider_ldap_enabled) 2018-11-28 11:19:19 +02:00
files/yum.repos.d Stop using patched synapse_port_db script 2017-10-14 09:58:06 +03:00
tasks Fix /.well-known/matrix/client for CORS 2018-11-29 09:13:25 +02:00
templates Fix /.well-known/matrix/client for CORS 2018-11-29 09:13:25 +02:00