Mistral serialiser and deserialiser can only work with entities in utf-8
Bug #1676411 reported by
Anastasia Kuznetsova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Invalid
|
Medium
|
Huang.Xiangdong |
Bug Description
During following bug https:/
there is no way to pass and process needed encoding parameter in Mistral serialiser and deserialiser.
For example, if action result is presented not in utf-8 encoding, that we will get error during its serialisation.
As a temporary workaround, there was proceed a decision to transform result from its encoding to UTF-8, but it is not a good solution from performance point of view.
So need to refactor serialiser and deserialiser to have an ability to work with any entity in any encoding.
Changed in mistral: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in mistral: | |
milestone: | none → rocky-3 |
assignee: | nobody → Huang.Xiangdong (privaterookie) |
To post a comment you must log in.
Mistral serialises the result to JSON, which must be UTF-8[1]
JSON text exchanged between systems that are not part of a closed
ecosystem MUST be encoded using UTF-8 [RFC3629]
Therefore, closing this as Invalid.
[1]: https:/ /tools. ietf.org/ html/rfc8259# section- 8.1