-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Labels
Description
Currently non-ascii text is not supported. For example if we have a JSON like
{"®":true}It would shows
{
"®": true
}reason: the registered trade mark sign is encoded in UTF-8 as C2 AE; when Burp see that, it breaks it into two characters C2 and AE. C2 becomes U+00C2 latin capital letter A with circumflex; AE becomes U+00AE registered trade mark sign.
I don’t know the solution, because ITextEditor is supposed to work like this (unless PortSwigger realize this and create ITextEditor.setText(String)). A solution is to migrate away from the default text editor; I understand that this is expensive.
Note that JSON should always be UTF-8. From RFC 8259, section “Character Encoding”:
JSON text exchanged between systems that are not part of a closed
ecosystem MUST be encoded using UTF-8 [RFC3629].