WebSockets via Rocket's Upgrade connection #1666

New Issue

MrUnknownDE · 2026-04-06T02:10:57+02:00

MrUnknownDE commented

2026-04-06 02:10:57 +02:00

Originally created by @BlackDex on 3/31/2023

This PR implements a (not yet fully released) new feature of Rocket which allows WebSockets/Upgrade connections.
No more need for multiple ports to be opened for Vaultwarden.
No explicit need for a reverse proxy to get WebSockets to work (Although I still suggest to use a reverse proxy).

Using a git revision for Rocket, since rocket_ws is not yet released.
Updated other crates as well.
Added a connection guard to clear the WS connection from the Users list.

Fixes #685
Fixes #2917
Fixes #1424

*Originally created by @BlackDex on 3/31/2023* This PR implements a (not yet fully released) new feature of Rocket which allows WebSockets/Upgrade connections. No more need for multiple ports to be opened for Vaultwarden. No explicit need for a reverse proxy to get WebSockets to work (Although I still suggest to use a reverse proxy). - Using a git revision for Rocket, since `rocket_ws` is not yet released. - Updated other crates as well. - Added a connection guard to clear the WS connection from the Users list. Fixes #685 Fixes #2917 Fixes #1424

MrUnknownDE closed this issue

2026-04-06 02:10:57 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1666