Detect UTF-8 encodings in Content-Type header
Currently request body and response body is decoded with Latin-1, inferred from question 17199168. The "Latin-1" is very ambiguous, but here I suppose "code page 1252" is referred to. According to HTTP standard, if Content-Type header specifies a "charset" directive, HTTP body should be decoded with that character encoding (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type#Directives). It would be great if this directive is respected.
Is this causing you a specific problem? If it is, let us know a bit more and we can usually suggest a workaround.
Burp does detect the charset directive in the Content-Type header when displaying messages. Otherwise, Burp is generally not Unicode aware. We may revisit this in the future, but it’s generally a reasonable choice for a security tool.
If it helps, the specific code page is ISO-8859-1.