mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-07-01 22:40:48 +00:00
9dad4c7c2d
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. |
||
|---|---|---|
| .. | ||
| configuring-dns.md | ||
| configuring-playbook-bridge-mautrix-telegram.md | ||
| configuring-playbook-bridge-mautrix-whatsapp.md | ||
| configuring-playbook-email.md | ||
| configuring-playbook-external-postgres.md | ||
| configuring-playbook-federation.md | ||
| configuring-playbook-ldap-auth.md | ||
| configuring-playbook-matrix-corporal.md | ||
| configuring-playbook-mxisd.md | ||
| configuring-playbook-own-webserver.md | ||
| configuring-playbook-rest-auth.md | ||
| configuring-playbook-s3.md | ||
| configuring-playbook-shared-secret-auth.md | ||
| configuring-playbook-telemetry.md | ||
| configuring-playbook.md | ||
| configuring-well-known.md | ||
| importing-sqlite.md | ||
| installing.md | ||
| maintenance-and-troubleshooting.md | ||
| maintenance-checking-services.md | ||
| maintenance-upgrading-postgres.md | ||
| maintenance-upgrading-services.md | ||
| prerequisites.md | ||
| README.md | ||
| registering-users.md | ||
| restoring-media-store.md | ||
| uninstalling.md | ||