28c255539c
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 |
||
|---|---|---|
| .. | ||
| ssl | ||
| init.yml | ||
| main.yml | ||
| self_check_well_known.yml | ||
| self_check_well_known_file.yml | ||
| setup_nginx_proxy.yml | ||
| setup_well_known.yml | ||
| validate_config.yml | ||