Skip to content

Stop the Mercure hub from accepting anonymous subscribers #287

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fashxp wants to merge 1 commit into from
Closed

Stop the Mercure hub from accepting anonymous subscribers #287

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docker-compose.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,14 @@ services:
SERVER_NAME: ':80'
MERCURE_PUBLISHER_JWT_KEY: 'CHANGE_ME_THIS_IS_MY_SECRET_KEY_THAT_IS_LONG_ENOUGH_FOR_VALIDATION'
MERCURE_SUBSCRIBER_JWT_KEY: 'CHANGE_ME_THIS_IS_MY_SECRET_KEY_THAT_IS_LONG_ENOUGH_FOR_VALIDATION'
MERCURE_EXTRA_DIRECTIVES: anonymous
# Deliberately no `anonymous` directive: the hub authorises a subscription once,
# when the EventSource connects, from the mercureAuthorization cookie. With
# anonymous subscribers allowed, a connection that carries no cookie (or one that
# expired while the tab stayed open) is answered 200 OK and then receives nothing,
# so Studio keeps what looks like a healthy stream while every notification, job
# progress update and agent chat event is dropped. Answering 401 instead makes the
# state visible and lets the client re-authorise.
MERCURE_EXTRA_DIRECTIVES: ''
# Uncomment the following line to enable the development mode
# command: /usr/bin/caddy run -config /etc/caddy/Caddyfile.dev
ports:
Expand Down
Loading