[GH-ISSUE #406] [BUG] The body of non UTF-8 Encoding HTML is displayed as Binary. #402

New issue

Open

opened 2026-03-03 19:18:17 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 19:18:17 +03:00

Owner

Originally created by @NghiaTranUIT on GitHub (Feb 23, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/406

Originally assigned to: @NghiaTranUIT on GitHub.

🐶 Brief

Some users report that some JP website, which is not UTF-8 Encoding, don't show the BODY as a text properly. It presents as a Binary.

We should fix it.

👑 Criteria

Make sure the Body is rendered as string properly with non UTF-8 encoding

Originally created by @NghiaTranUIT on GitHub (Feb 23, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/406 Originally assigned to: @NghiaTranUIT on GitHub. ## 🐶 Brief Some users report that some JP website, which is not UTF-8 Encoding, don't show the BODY as a text properly. It presents as a Binary. We should fix it. ## 👑 Criteria - [ ] Make sure the Body is rendered as string properly with non UTF-8 encoding

kerem added the

bug

✅ Done

labels

2026-03-03 19:18:17 +03:00

kerem commented

2026-03-03 19:18:18 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Feb 24, 2020):

BETA build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.16.0_Fix_Content-Encoding.dmg

This build will get the charset from Content-Type or automatically detect the encoding to parse to string properly.

@NghiaTranUIT commented on GitHub (Feb 24, 2020): - BETA build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.16.0_Fix_Content-Encoding.dmg This build will get the charset from Content-Type or automatically detect the encoding to parse to string properly. <img width="2032" alt="Screen Shot 2020-02-24 at 14 31 25" src="https://user-images.githubusercontent.com/5878421/75135006-b0797880-5712-11ea-8d2a-29f71fd44159.png">