7 Commits (3a9fe48deb025b5d49256675bf563f81c39f910b)

Author	SHA1	Message	Date
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	3 years ago
shadow	6293f1bdb0	Run all API self checks in check_mode	4 years ago
Dan Arnfield	86eff45e8b	uri.follow_redirects is now a string field	5 years ago
Slavi Pantaleev	73af8f7bbb	Make self-check not validate self-signed certificates ... By default, `--tags=self-check` no longer validates certificates when `matrix_ssl_retrieval_method` is set to `self-signed`. Besides this default, people can also enable/disable validation using the individual role variables manually. Fixes #124 (Github Issue)	5 years ago
Slavi Pantaleev	a43bcd81fe	Rename some variables	5 years ago
Slavi Pantaleev	25bdc10617	Follow redirects for some well-known files ... The Server spec says that redirects should be followed for `/.well-known/matrix/server`. So we follow them. The Client-Server specs doesn't mention redirects, so we don't follow redirects there.	5 years ago
Slavi Pantaleev	f6ebd4ce62	Initial work on Synapse 0.99/1.0 preparation	5 years ago