When I capture HTTP requests and responses with Burp suite, everything works fine except when I want to capture facebook.com responses, I get a strange response body which is in some unreadable format that is not HTML, but just some strange symbols (the response headers are ok and readable, but the body is not). Does anybody have an idea what could be the reason for that and if there is a fix? The burp cert is configured in my browser. And the response renders fine in my browser.
The response headers (without some values for which I'm not sure if I should post them) are:
HTTP/1.1 200 OK P3P: CP="Facebook does not have a P3P policy. Learn why here: http://fb.me/p3p" X-Frame-Options: DENY X-XSS-Protection: 0 X-Content-Type-Options: nosniff public-key-pins-report-only: Pragma: no-cache content-security-policy: default-src * data: blob:;script-src *.facebook.com *.fbcdn.net *.facebook.net *.google-analytics.com *.virtualearth.net *.google.com 127.0.0.1:* *.spotilocal.com:* 'unsafe-inline' 'unsafe-eval' fbstatic-a.akamaihd.net fbcdn-static-b-a.akamaihd.net *.atlassolutions.com blob: data:;style-src data: 'unsafe-inline' *;connect-src *.facebook.com *.fbcdn.net *.facebook.net *.spotilocal.com:* *.akamaihd.net wss://*.facebook.com:* https://fb.scanandcleanlocal.com:* *.atlassolutions.com attachment.fbsbx.com ws://localhost:* blob:; Cache-Control: private, no-cache, no-store, must-revalidate Strict-Transport-Security: max-age=15552000; preload Vary: Accept-Encoding Content-Encoding: br Content-Type: text/html X-FB-Debug: Date: Mon, 05 Sep 2016 22:09:00 GMT Connection: close
And the first few bytes of the response body in HEX look like this:
0a 07 30 0c 00 e4 af 9f ab fe f7 e7 cb 7a 7b 41