vaultwarden/src
Mathijs van Veluw 0fdda3bc2f
Prevent generating an error during ws close (#4127)
When a WebSocket connection was closing it was sending a message after
it was closed already. This generated an error in the logs.
While this error didn't harm any of the functionallity of Vaultwarden it
isn't nice to see them of course.

This PR Fixes this by catching the close message and breaks the loop at
that point. This prevents the `_` catch-all from replying the close
message back to the client, which was causing the error message.

Fixes #4090
2023-12-04 20:20:13 +01:00
..
api Prevent generating an error during ws close (#4127) 2023-12-04 20:20:13 +01:00
db Update crates (#4074) 2023-11-15 10:41:14 +01:00
static Add Protected Actions Check (#4067) 2023-11-12 22:15:44 +01:00
auth.rs Allow Authorization header for Web Sockets 2023-08-31 12:35:20 +02:00
config.rs Add Protected Actions Check (#4067) 2023-11-12 22:15:44 +01:00
crypto.rs Remove get_random_64() 2022-11-13 10:03:06 +01:00
error.rs Update crates (#4074) 2023-11-15 10:41:14 +01:00
mail.rs Add Protected Actions Check (#4067) 2023-11-12 22:15:44 +01:00
main.rs tokio::signal::unix::SignalKind::hangup().as_raw_value() insted of 1 2023-10-21 17:14:03 +02:00
ratelimit.rs Basic ratelimit for user login (including 2FA) and admin login 2021-12-22 21:48:49 +01:00
util.rs Update crates (#4074) 2023-11-15 10:41:14 +01:00