Support Matrix server discovery (.well-known) - #27
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 15 out of 15 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
fmartingr
approved these changes
Jan 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements Matrix server discovery (.well-known/matrix/server) to support deployments where the Matrix homeserver URL differs from the Matrix ID domain. Fixes #14.
Organizations commonly use Matrix server discovery to separate their homeserver location from their Matrix ID domain. For example:
This is configured via
.well-known/matrix/server: { "m.server": "matrix.example.com:443" }Previously, the plugin derived the Matrix ID domain directly from the homeserver URL hostname, causing Matrix IDs to be constructed incorrectly as @user:matrix.example.com instead of @user:example.com.
This is implemented with three-tier server name resolution:
Ticket Link
fixes #14