Skip to content

Clarify that clients must avoid producing ambiguous matrix.to URIs#2396

Open
HarHarLinks wants to merge 3 commits into
matrix-org:mainfrom
HarHarLinks:patch-10
Open

Clarify that clients must avoid producing ambiguous matrix.to URIs#2396
HarHarLinks wants to merge 3 commits into
matrix-org:mainfrom
HarHarLinks:patch-10

Conversation

@HarHarLinks

@HarHarLinks HarHarLinks commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

The spec already says this, yet clients tend to ignore what is clearly a requirement here, so this is an attempt to clarify. Note the notice further down about still trying to interpret unencoded (incorrect) URIs at best effort is left intact.

See also matrix-org/matrix.to#404.

Updated the section about matrix.to with RFC 2119 lingo while at it.

Pull Request Checklist

Preview: https://pr2396--matrix-spec-previews.netlify.app

@HarHarLinks HarHarLinks requested a review from a team as a code owner June 10, 2026 12:31
@HarHarLinks HarHarLinks requested a review from zecakeh as a code owner June 23, 2026 15:05

@anoadragon453 anoadragon453 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing all the lowercase verbiage!

Comment thread content/appendices.md

The components of the matrix.to URI (`<identifier>` and
`<extra parameter>`) MUST be percent-encoded as per RFC 3986.
Clients MUST NOT produce incorrectly encoded URIs to avoid ambiguous interpretation.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Clients MUST NOT produce incorrectly encoded URIs to avoid ambiguous interpretation.
Clients MUST NOT produce incorrectly encoded URIs to avoid ambiguous
interpretation.

Comment thread content/appendices.md

The components of the matrix.to URI (`<identifier>` and
`<extra parameter>`) MUST be percent-encoded as per RFC 3986.
Clients MUST NOT produce incorrectly encoded URIs to avoid ambiguous interpretation.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What point is this making other than making the previous statement harder to skim over? Assuming that "incorrectly encoded" means "not percent-encoded".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"incorrectly encoded" means "not encoded according to spec" 🤷

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