Skip to content

Maintenance: Document the FQDN requirement for the real-time channel. - #1337

Merged
ralf401 merged 1 commit into
pre-releasefrom
rsc/maintenance/fqdn-realtime-origin
Oct 8, 2026
Merged

ralf401 merged 1 commit into
pre-releasefrom
rsc/maintenance/fqdn-realtime-origin

Conversation

@ralf401

@ralf401 ralf401 commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

The legacy WebSocket authenticates from the session cookie of its handshake and only trusts it when the Origin header matches <http_type>:// (lib/sessions/event/login.rb in zammad/zammad; see also the BREAKING_CHANGES.md entry "The legacy WebSocket login is authenticated from the session cookie and signshow no longer returns session_id").

The legacy WebSocket authenticates from the session cookie of its handshake and only trusts it when the Origin header matches <http_type>://<fqdn> (lib/sessions/event/login.rb in zammad/zammad; see also the BREAKING_CHANGES.md entry "The legacy WebSocket login is authenticated from the session cookie and signshow no longer returns session_id").

The FQDN setting entry now states that the value, together with the HTTP type, is the trusted origin for the real-time channel. Regenerated locale/admin-docs.pot via make gettext.
@github-actions

github-actions Bot commented Oct 8, 2026

Copy link
Copy Markdown

Artifacts

Produced during runtime

📦 html-96df5a7

@ralf401
ralf401 merged commit a67e73d into pre-release Oct 8, 2026
1 check passed
@ralf401
ralf401 deleted the rsc/maintenance/fqdn-realtime-origin branch October 8, 2026 12:16
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.

1 participant