-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
Given that the server can return invalid UTF-8 sequences, it seems safer to handle them gracefully in the driver by default rather than via our special Document::from_reader_utf8_lossy. This is currently the behavior in the Node and Python drivers.
Acceptance Criteria
- When decoding server errors use lossy decoding
- is related to
-
SERVER-24007 Server can return invalid UTF8 for error messages due to truncation in the middle of a code point
- Backlog
-
DRIVERS-2008 Default to lossy/replacement behavior when decoding UTF-8 in writeErrors
- Backlog