Alexandros Afentoulis 28c255539c matrix-nginx-proxy: specify Origin header, comply with CORS ... Self-checks against the .well-known URIs look for the HTTP header "Access-Control-Allow-Origin" indicating that the remode endpoint supports CORS. But the remote server is not required to include said header in the response if the HTTP request does not include the "Origin" header. This is in accordance with the specification [1] stating: 'A CORS request is an HTTP request that includes an "Origin" header.' This is in fact true for Gitlab pages hosting and that's why the issue was identified. Let's specify "Origin" header in the respective uri tasks performing the HTTP request and ensure a CORS request. [1] https://fetch.spec.whatwg.org/#http-requests		2021-03-15 14:24:55 +02:00
..
ssl	Do not delete matrix-ssl-lets-encrypt-certificates-renew only to recreate it later	2021-02-26 13:37:51 +02:00
init.yml	Replace cronjobs with systemd timers	2021-01-14 23:35:50 +02:00
main.yml	Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8	2019-05-21 10:25:59 -05:00
self_check_well_known_file.yml	matrix-nginx-proxy: specify Origin header, comply with CORS	2021-03-15 14:24:55 +02:00
self_check_well_known.yml	Rename variables (s/mxisd/ma1sd/) and adapt roles	2020-04-02 11:31:38 +02:00
setup_nginx_proxy.yml	Merge branch 'master' into synapse-workers	2021-02-14 13:00:57 +02:00
setup_well_known.yml	Allow the matrix user username and groupname to be configured separately	2020-05-01 19:59:32 +02:00
validate_config.yml	Remove unused variable	2021-01-14 17:47:13 +02:00