fossilfranv/matrix-docker-ansible-deploy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

make self-check of /.well-known/matrix/server accept redirects

Browse Source 
Rationale: the /.well-known/matrix/client should return only 200 as well, but it has hardcoded "safe" value, regardless the spec: https://spec.matrix.org/v1.4/client-server-api/#well-known-uri

So, why not do the same for the /.well-known/matrix/server?
This commit is contained in:
Aine 2022-10-26 11:04:17 +00:00 committed by GitHub
parent 3694bf1d18
commit 21eabf45c2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
roles/matrix-nginx-proxy/defaults/main.yml
View File

@ -489,9 +489,9 @@ matrix_nginx_proxy_self_check_validate_certificates: true
# Controls whether redirects will be followed when checking the `/.well-known/matrix/client` resource. # Controls whether redirects will be followed when checking the `/.well-known/matrix/client` resource.
# #
# As per the spec (https://matrix.org/docs/spec/client_server/r0.6.0#well-known-uri), it shouldn't be, # As per the spec (https://spec.matrix.org/v1.4/client-server-api/#well-known-uri), it shouldn't be,
# so we default to not following redirects as well. # but in real life all client apps and servers accept the 301 redirect.
matrix_nginx_proxy_self_check_well_known_matrix_client_follow_redirects: none matrix_nginx_proxy_self_check_well_known_matrix_client_follow_redirects: safe
# For OCSP purposes, we need to define a resolver at the `server{}` level or `http{}` level (we do the latter). # For OCSP purposes, we need to define a resolver at the `server{}` level or `http{}` level (we do the latter).
# #