matrix-docker-ansible-deploy/roles/matrix-server/tasks/self_check
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
..
main.yml Relocate some playbook task files to make it easier to navigate 2018-10-21 13:14:47 +03:00
self_check_client_api.yml
self_check_corporal.yml
self_check_dns.yml
self_check_federation_api.yml
self_check_mxisd.yml
self_check_riot_web.yml
self_check_well_known.yml Fix /.well-known/matrix/client for CORS 2018-11-29 09:13:25 +02:00