Skip to content

Add enableClientWellKnownLookups#4103

Draft
langleyd wants to merge 2 commits into
livekitfrom
langleyd/enable-wellknown-lookup
Draft

Add enableClientWellKnownLookups#4103
langleyd wants to merge 2 commits into
livekitfrom
langleyd/enable-wellknown-lookup

Conversation

@langleyd

@langleyd langleyd commented Jul 10, 2026

Copy link
Copy Markdown
Member

Adds gating (default on) so a deployment can stop Element Call making client
.well-known requests to the homeserver server_name. Set via the
enableClientWellKnownLookups URL param in widget mode (by the embedder) and
enable_client_well_known_lookups in config.json in SPA mode; resolution is
URL param → config → default on.

  • Off: always avoid client .well-known — skips the post-login poll
    (widget.ts widget mode, utils/matrix.ts SPA mode) and the legacy MatrixRTC
    foci fallback.
  • On/unset: respect the server — only fall back to .well-known for
    transports on a 404 M_UNRECOGNIZED; any other response is authoritative.

Element web embedded:
Complementary to element-hq/element-web#34084.
If removeelement_call.disable in EW config but keep enable_client_well_known_lookups EC will continue to respect it (as long as it passes in the URL Param).

matrix-org/matrix-js-sdk#5245 can then be added on top and will allow EC to function in EW alongside enable_client_well_known_lookups.

Gate client well-known lookups on enableClientWellKnownLookups

New URL param (default on), threaded from the embedder. When off, always
avoid client .well-known: skip the post-login poll (widget + SPA) and the
legacy MatrixRTC foci fallback. When on/unset, respect the transports
endpoint response: only fall back to .well-known on a 404 M_UNRECOGNIZED.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants