[GH-ISSUE #1482] Content-type application/json request shows as binary data #1477

Open
opened 2026-03-03 19:51:48 +03:00 by kerem · 4 comments
Owner

Originally created by @headquarters on GitHub (Dec 31, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1482

Originally assigned to: @NghiaTranUIT on GitHub.

Description

I've been a long time Charles Proxy user and found it to be nearly unusable on an M1 MacBook Air. Proxyman, however, is excellent! Great UI, very responsive, and has all the features I want. I've hit one major blocker to adopting it, though: requests to one application that work in Charles Proxy do not work in Proxyman. They are content-type application/json requests but show up as in the UI.

Steps to Reproduce

  1. Open Proxyman
  2. Enable SSL for this particular app (can share details via email or DM)
  3. View requests and responses
  4. Requests that are JSON content show as

Current Behavior

Screenshot from Proxyman:
Screenshot 2022-12-30 at 8 46 40 PM

All requests for this app show binary data for the JSON data in Proxyman. However, in Charles Proxy and in MITM Proxy these same requests show JSON data.

Expected Behavior

I would expect that application/json requests would show JSON data in the UI.

Environment

  • App version: e.g Proxyman 3.15.0
  • macOS version: Ventura 13.1 (MacBook Air M2)
Originally created by @headquarters on GitHub (Dec 31, 2022). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1482 Originally assigned to: @NghiaTranUIT on GitHub. ## Description I've been a long time Charles Proxy user and found it to be nearly unusable on an M1 MacBook Air. Proxyman, however, is excellent! Great UI, very responsive, and has all the features I want. I've hit one major blocker to adopting it, though: requests to one application that work in Charles Proxy do not work in Proxyman. They are content-type application/json requests but show up as <binary data> in the UI. ## Steps to Reproduce 1. Open Proxyman 2. Enable SSL for this particular app (can share details via email or DM) 3. View requests and responses 4. Requests that are JSON content show as <binary data> ## Current Behavior Screenshot from Proxyman: <img width="1131" alt="Screenshot 2022-12-30 at 8 46 40 PM" src="https://user-images.githubusercontent.com/347079/210121479-a3559db0-9a2a-4159-8aff-ded14a312518.png"> All requests for this app show binary data for the JSON data in Proxyman. However, in Charles Proxy and in MITM Proxy these same requests show JSON data. <!--- What went wrong? --> ## Expected Behavior I would expect that application/json requests would show JSON data in the UI. <!--- What should have happened? --> ## Environment - App version: e.g Proxyman 3.15.0 - macOS version: Ventura 13.1 (MacBook Air M2)
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 31, 2022):

@headquarters please try using this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.15.0_Fix_gzip_decoder.dmg

The problem was the Content-Encoding: GZIP (GZIP is Uppercase, so Proxyman could not detect it).

<!-- gh-comment-id:1368176034 --> @NghiaTranUIT commented on GitHub (Dec 31, 2022): @headquarters please try using this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.15.0_Fix_gzip_decoder.dmg The problem was the `Content-Encoding: GZIP` (GZIP is Uppercase, so Proxyman could not detect it).
Author
Owner

@headquarters commented on GitHub (Dec 31, 2022):

@NghiaTranUIT Thanks for the quick turnaround on that! I tested that build but still no luck, same binary data showing in response. I sent a new log to support for review.

<!-- gh-comment-id:1368214727 --> @headquarters commented on GitHub (Dec 31, 2022): @NghiaTranUIT Thanks for the quick turnaround on that! I tested that build but still no luck, same binary data showing in response. I sent a new log to support for review.
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 1, 2023):

@headquarters Sorry for my mistake 🙇 . It's fixed again with this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.15.0_Fix_Content_Encoding_v2.dmg

<!-- gh-comment-id:1368339866 --> @NghiaTranUIT commented on GitHub (Jan 1, 2023): @headquarters Sorry for my mistake 🙇 . It's fixed again with this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.15.0_Fix_Content_Encoding_v2.dmg
Author
Owner

@headquarters commented on GitHub (Jan 1, 2023):

That fixed it! Thank you so much.

<!-- gh-comment-id:1368423579 --> @headquarters commented on GitHub (Jan 1, 2023): That fixed it! Thank you so much.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#1477
No description provided.