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
main.yml
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
setup_nginx_proxy.yml
setup_well_known.yml
validate_config.yml