Add config param to disable client wellknown fetch (#34084)

* Add enable_client_well_known_lookups config option Signed-off-by: David Langley <langley.dave@gmail.com> * Gate client .well-known poll on enable_client_well_known_lookups Signed-off-by: David Langley <langley.dave@gmail.com> * Gate MatrixRTC foci well-known fallback on enable_client_well_known_lookups Signed-off-by: David Langley <langley.dave@gmail.com> --------- Signed-off-by: David Langley <langley.dave@gmail.com> Co-authored-by: David Langley <langley.dave@gmail.com>
2026-07-13 15:27:36 +00:00
parent c4606c19f8
commit 6aeb5f552b
7 changed files with 71 additions and 5 deletions
@@ -57,6 +57,12 @@ If both `default_server_config` and `default_server_name` are used, Element will
 information using `.well-known`, and if that fails, take `default_server_config` as the homeserver connection
 information.

+1. `enable_client_well_known_lookups`: Controls whether Element makes runtime requests to the logged-in user's
+   [`<server_name>/.well-known/matrix/...`](https://spec.matrix.org/latest/client-server-api/#getwell-knownmatrixclient)
+   endpoints (for example, polling for client configuration after login). Set it to `false` to stop Element making these
+   requests, so it only contacts the homeserver base URL; the `well_known` object returned inline in the `/login` response
+   is unaffected. Defaults to `true`.
+
 ## Labs flags

 Labs flags are optional, typically beta or in-development, features that can be turned on or off. The full range of