Skip to content

[stable5.13] fix(deeplink): encode message-id as base64url for deep links - #14264

Merged
ChristophWurst merged 1 commit into
stable5.13from
backport/14023/stable5.13
Nov 20, 2026
Merged

ChristophWurst merged 1 commit into
stable5.13from
backport/14023/stable5.13

Conversation

@backportbot

@backportbot backportbot Bot commented Nov 20, 2026

Copy link
Copy Markdown

Backport of PR #14023

RFC 5322 permits characters in Message-IDs (such as slashes, quotes,
etc., commonly seen in GitHub notifications or Bugzilla/GitLab messages)
that are problematic in URL paths. When generating a deep link in the
Unified Search provider (mail.deep_link.open) or copying a direct link,
Symfony's UrlGenerator threw an InvalidParameterException or web servers
failed to route slashes.

Encode Message-IDs using URL-safe base64url via a Base64Url helper in
the search provider and envelope menu, and decode it in
DeepLinkController::open(). Unencoded Message-IDs are still accepted
for backwards compatibility by checking for the mandatory '@' symbol.
If a message lacks a Message-ID, the search provider falls back to
the direct thread link.

Fixes #13970

Signed-off-by: SoleroTG <github-29h@solero.quietmail.eu>
@ChristophWurst
ChristophWurst force-pushed the backport/14023/stable5.13 branch from 4fa57af to c47b1da Compare November 20, 2026 17:08
@ChristophWurst
ChristophWurst merged commit bea5a50 into stable5.13 Nov 20, 2026
44 of 45 checks passed
@ChristophWurst
ChristophWurst deleted the backport/14023/stable5.13 branch November 20, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants