[GH-ISSUE #1539] Proxyman struggling with json escape in pretty json #1532

New issue

Open

opened 2026-03-03 19:52:15 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 19:52:15 +03:00

Owner

Originally created by @novitae on GitHub (Feb 12, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1539

Originally assigned to: @NghiaTranUIT on GitHub.

Description

Proxyman struggles with json escape in pretty json

Steps to Reproduce

Send a request with the following body (Content-Type: application/x-www-form-urlencoded; charset=UTF-8):

signed_body=SIGNATURE.%7B%22_uuid%22%3A%22BC######E-A4A9-4C18-B340-ACC9F0A4E4F0%22%2C%22_uid%22%3A%22%22%2C%22params%22%3A%22%7B%5C%22server_params%5C%22%3A%7B%5C%22flow_info%5C%22%3A%5C%22%7B%5C%5C%5C%22flow_name%5C%5C%5C%22%3A%5C%5C%5C%22new_to_family_ig_default%5C%5C%5C%22%2C%5C%5C%5C%22flow_type%5C%5C%5C%22%3A%5C%5C%5C%22ntf%5C%5C%5C%22%7D%5C%22%7D%7D%22%2C%22bloks_versioning_id%22%3A%22ff640ee461de95ec0b83db17fb5abe01e35809d0a357ee54d557aaeba0b3cbaf%22%7D

In the form field of the request, at the field signed_body, select the json part after SIGNATURE.
Right-click it, and click on Pretty json

Current Behavior

The pretty json window displays the message <Invalid JSON String. Please selected again!>, while the json is absolutely valid and can be loaded.
Capture d’écran 2023-02-12 à 11 24 34

Expected Behavior

It should load the json correctly. This is probably due to string escape, I noticed it works when there aren't in the payload.

Environment

App version: Proxyman 4.2.1
macOS version: macOS Ventura 13.2

Originally created by @novitae on GitHub (Feb 12, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1539 Originally assigned to: @NghiaTranUIT on GitHub. ## Description Proxyman struggles with json escape in pretty json ## Steps to Reproduce 1. Send a request with the following body (`Content-Type: application/x-www-form-urlencoded; charset=UTF-8`): ``` signed_body=SIGNATURE.%7B%22_uuid%22%3A%22BC######E-A4A9-4C18-B340-ACC9F0A4E4F0%22%2C%22_uid%22%3A%22%22%2C%22params%22%3A%22%7B%5C%22server_params%5C%22%3A%7B%5C%22flow_info%5C%22%3A%5C%22%7B%5C%5C%5C%22flow_name%5C%5C%5C%22%3A%5C%5C%5C%22new_to_family_ig_default%5C%5C%5C%22%2C%5C%5C%5C%22flow_type%5C%5C%5C%22%3A%5C%5C%5C%22ntf%5C%5C%5C%22%7D%5C%22%7D%7D%22%2C%22bloks_versioning_id%22%3A%22ff640ee461de95ec0b83db17fb5abe01e35809d0a357ee54d557aaeba0b3cbaf%22%7D ``` 2. In the `form` field of the request, at the field `signed_body`, select the json part after `SIGNATURE.` 3. Right-click it, and click on `Pretty json` ## Current Behavior The pretty json window displays the message `<Invalid JSON String. Please selected again!>`, while the json is absolutely valid and can be loaded. <img width="985" alt="Capture d’écran 2023-02-12 à 11 24 34" src="https://user-images.githubusercontent.com/85891169/218305530-e7bc4ee6-21c9-432f-a933-693878d8ed31.png"> <img width="1235" alt="Capture d’écran 2023-02-12 à 11 22 35" src="https://user-images.githubusercontent.com/85891169/218305450-0ce887fa-9924-4598-93b7-27db5b736995.png"> ## Expected Behavior It should load the json correctly. This is probably due to string escape, I noticed it works when there aren't in the payload. ## Environment - App version: Proxyman 4.2.1 - macOS version: macOS Ventura 13.2

kerem added the

bug

✅ Done

labels

2026-03-03 19:52:15 +03:00

kerem commented

2026-03-03 19:52:15 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Feb 13, 2023):

@novitae let's try this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_4.2.1_Fix_inline_JSON_Prettify.dmg

It fixes your special escaping JSON String 👍

@NghiaTranUIT commented on GitHub (Feb 13, 2023): @novitae let's try this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_4.2.1_Fix_inline_JSON_Prettify.dmg It fixes your special escaping JSON String 👍 ![Screenshot_2023-02-13_at_12_54_26](https://user-images.githubusercontent.com/5878421/218381520-cc0398a4-b273-4631-9e8b-5452b3db0eb6.jpg)