Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Detect UTF-8 encodings in Content-Type header

Zhaolin | Last updated: May 25, 2018 10:27PM UTC

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.

PortSwigger Agent | Last updated: May 29, 2018 06:35AM UTC

Hi Zhaolin, 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.

Burp User | Last updated: Jan 28, 2020 08:05AM UTC

My language is Thai so it's cant decode or display in Burp Suite, while OWASP ZAP can. It affects to do test on website.

Michelle, PortSwigger Agent | Last updated: Jan 28, 2020 10:11AM UTC