JSONRESTView named operation handler needs to decode POST data as UTF-8
Bug #492525 reported by
William Grant
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| IVLE |
Triaged
|
High
|
Unassigned | ||
Bug Description
Named operations in JSONRESTView derivatives currently cast lots of input
to unicode. That is very bad of them.
Unfortunately, JSONRESTView left them no choice - it gives named operation
functions strs! It should instead assume that the POST data is encoded as
UTF-8, decode it, and pass in unicodes instead.
Revision history for this message
| William Grant (wgrant) wrote | #1 |
| Changed in ivle: | |
| assignee: | William Grant (wgrant) → nobody |
| tags: | added: refactor |
To post a comment you must log in.
This is more difficult than it could be, as the current JSONRESTView consumers all do the decoding manually. Once JSONRESTView starts to decode strings itself, they will all break.