mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #1482] Content-type application/json request shows as binary data #1477
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1477
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Current Behavior
Screenshot from Proxyman:

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
@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).@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.
@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
@headquarters commented on GitHub (Jan 1, 2023):
That fixed it! Thank you so much.