geforkt von mirrored/vaultwarden
Avoid Error parsing LastKnownRevisionDate
warning for mobile clients
When creating a new cipher, the mobile clients seem to set this field to an invalid value, which causes a warning to be logged: Error parsing LastKnownRevisionDate '0001-01-01T00:00:00': premature end of input Avoid this by dropping the `LastKnownRevisionDate` field on cipher creation.
Dieser Commit ist enthalten in:
Ursprung
9254cf9d9c
Commit
49579e4ce7
1 geänderte Dateien mit 7 neuen und 1 gelöschten Zeilen
|
@ -268,7 +268,13 @@ fn post_ciphers_create(data: JsonUpcase<ShareCipherData>, headers: Headers, conn
|
|||
/// Called when creating a new user-owned cipher.
|
||||
#[post("/ciphers", data = "<data>")]
|
||||
fn post_ciphers(data: JsonUpcase<CipherData>, headers: Headers, conn: DbConn, nt: Notify) -> JsonResult {
|
||||
let data: CipherData = data.into_inner().data;
|
||||
let mut data: CipherData = data.into_inner().data;
|
||||
|
||||
// The web/browser clients set this field to null as expected, but the
|
||||
// mobile clients seem to set the invalid value `0001-01-01T00:00:00`,
|
||||
// which results in a warning message being logged. This field isn't
|
||||
// needed when creating a new cipher, so just ignore it unconditionally.
|
||||
data.LastKnownRevisionDate = None;
|
||||
|
||||
let mut cipher = Cipher::new(data.Type, data.Name.clone());
|
||||
update_cipher_from_data(&mut cipher, data, &headers, false, &conn, &nt, UpdateType::CipherCreate)?;
|
||||
|
|
Laden …
In neuem Issue referenzieren