diff options
| author | engn33r <engn33r@users.noreply.github.com> | 2022-05-09 18:49:09 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-09 18:49:09 +0000 |
| commit | fc9ee9f82f66fa40da30d4fd207b7f641e7f6f62 (patch) | |
| tree | 094d3ad228b15d47b722ebb4c66d6e9bfb1c156c | |
| parent | fbf061a9a0dd9ce533bc3c7b3486f517a31b5514 (diff) | |
| download | websocket-client-fc9ee9f82f66fa40da30d4fd207b7f641e7f6f62.tar.gz | |
Add utf8 encoding error workaround
| -rw-r--r-- | docs/source/faq.rst | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/docs/source/faq.rst b/docs/source/faq.rst index 30a4ecc..fad8c6b 100644 --- a/docs/source/faq.rst +++ b/docs/source/faq.rst @@ -88,7 +88,16 @@ If you use the ``Sec-WebSocket-Extensions: permessage-deflate`` header with websocket-client, you will probably encounter errors, such as the ones described in `issue #314. <https://github.com/websocket-client/websocket-client/tree/master/compliance>`_ -If a connection is re-establish after getting disconnected, does the new connection continue where the previous one dropped off? +I get the error 'utf8' codec can't decode byte 0x81 in position 0 +============================================================================ + +This error is caused when you receive a character that is not a UTF-8 character, +so the UTF-8 decoding fails. You can set `skip_utf8_validation` to false, +but if this does not work, you can change the encoding to ISO-8859-1 which +was a workaround suggested in +[issue 481](https://github.com/websocket-client/websocket-client/issues/481#issuecomment-1112506666). + +If a connection is re-established after getting disconnected, does the new connection continue where the previous one dropped off? ======================================================================================================================================= The answer to this question depends on how the WebSocket server |