1
Documentation insondistency concerning websocket notifications
Source: dani-garcia/vaultwarden#3638 · opened by @sheerun
It says "Note: The reason for this workaround is the lack of support for WebSockets from Rocket (though it's a planned feature), which forces us to launch a secondary server on a separate port."
I think it is not up do date because "it's a planned feature" links to which is closed
I think it is not up do date because "it's a planned feature" links to which is closed
No pledges yet. Be the first to back this.
Comments
Similar requests
Protect Admin panel by restricting access to only IP LAN
2 votes · 0 comments
Issue: WebSocket Token in URI
1 vote · 0 comments
My items collection is not created when enabling Enforce organization ownership
4 votes · 0 comments
Long invitation links (JWT tokens) broken by quoted-printable encoding in some email clients (SOGo / K-9)
1 vote · 0 comments
Consider `invitation_org_name` and `smtp_from_name` to be sensitive as well for `Generate Support String`
1 vote · 0 comments
No comments yet.