starred/proxyman-windows-linux

Fork 0

mirror of https://github.com/ProxymanApp/proxyman-windows-linux.git synced 2026-05-04 20:31:10 +03:00

[GH-ISSUE #460] Proxyman 2.19.0 on Windows: Incomplete Display of Hexadecimal Request Bodies and Lack of JSON Decoding Support #458

New issue

Open

opened 2026-03-03 19:50:42 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 19:50:42 +03:00

Owner

Originally created by @aa1134665908 on GitHub (Dec 31, 2024).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/460

Originally assigned to: @kics223w1 on GitHub.

Description
When using Proxyman version 2.19.0 on Windows to view request bodies containing hexadecimal data, the application fails to display the complete content. Additionally, the Windows version lacks JSON compatibility for decoding such content.

Steps to Reproduce
Install Proxyman version 2.19.0 on a Windows system.

Intercept a request containing hexadecimal data in the body.

Attempt to view the full request body in Proxyman.

Try to use JSON decoding for the hexadecimal content.

Current Behavior
Proxyman fails to display the complete hexadecimal content in the request body.
The Windows version does not provide JSON compatibility for decoding the hexadecimal data.
Expected Behavior
Proxyman should display the full hexadecimal content in the request body without truncation.
The Windows version should offer JSON compatibility or an alternative method to properly decode and display hexadecimal data.
Environment
App version: Proxyman 2.19.0
Windows/Linux version: Windows (latest version)

https://github.com/user-attachments/assets/ee2a3802-abab-454d-b111-2ad4492d2951

Originally created by @aa1134665908 on GitHub (Dec 31, 2024). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/460 Originally assigned to: @kics223w1 on GitHub. Description When using Proxyman version 2.19.0 on Windows to view request bodies containing hexadecimal data, the application fails to display the complete content. Additionally, the Windows version lacks JSON compatibility for decoding such content. Steps to Reproduce Install Proxyman version 2.19.0 on a Windows system. Intercept a request containing hexadecimal data in the body. Attempt to view the full request body in Proxyman. Try to use JSON decoding for the hexadecimal content. Current Behavior Proxyman fails to display the complete hexadecimal content in the request body. The Windows version does not provide JSON compatibility for decoding the hexadecimal data. Expected Behavior Proxyman should display the full hexadecimal content in the request body without truncation. The Windows version should offer JSON compatibility or an alternative method to properly decode and display hexadecimal data. Environment App version: Proxyman 2.19.0 Windows/Linux version: Windows (latest version) https://github.com/user-attachments/assets/ee2a3802-abab-454d-b111-2ad4492d2951

kerem added the

✅ Done

bug

labels

2026-03-03 19:50:42 +03:00

kerem commented

2026-03-03 19:50:43 +03:00

Author

Owner

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

@aa1134665908 are you sure it's a JSON Text? It looks like it's encoded by some algorithm. If yes, please check the Content-Encoding header in your Request and share with me.

By default, if the body is text base, Proxyman tries to parse it as a JSON and prettify it

@NghiaTranUIT commented on GitHub (Dec 31, 2024): @aa1134665908 are you sure it's a JSON Text? It looks like it's encoded by some algorithm. If yes, please check the `Content-Encoding` header in your Request and share with me. By default, if the body is text base, Proxyman tries to parse it as a JSON and prettify it

kerem commented

2026-03-03 19:50:43 +03:00

Author

Owner

@aa1134665908 commented on GitHub (Dec 31, 2024):

@aa1134665908 are you sure it's a JSON Text? It looks like it's encoded by some algorithm. If yes, please check the Content-Encoding header in your Request and share with me.

By default, if the body is text base, Proxyman tries to parse it as a JSON and prettify it

Thank you for your request for more information. I can provide you with the headers of a request that demonstrates this issue:

user-agent: Mozilla/5.0 (Linux; U; Android 4.1.1; ja-jp; T-01D Build/F0001) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1 NEWSAY
connection: close
accept-encoding: identity
content-type: application/json; charset=utf-8
content-length: 172

As you can see, the content-type is set to application/json with UTF-8 charset. However, the body contains hexadecimal data, not JSON. In the Mac version, Proxyman automatically handles this discrepancy and displays the data correctly. In the Windows version (2.19.0), the hexadecimal data is not fully displayed, and there's no option to decode it properly.

Could you please investigate why the Windows version is unable to display the full hexadecimal content and why it lacks the automatic decoding feature present in the Mac version?

@aa1134665908 commented on GitHub (Dec 31, 2024): > @aa1134665908 are you sure it's a JSON Text? It looks like it's encoded by some algorithm. If yes, please check the `Content-Encoding` header in your Request and share with me. > > By default, if the body is text base, Proxyman tries to parse it as a JSON and prettify it Thank you for your request for more information. I can provide you with the headers of a request that demonstrates this issue: ``` user-agent: Mozilla/5.0 (Linux; U; Android 4.1.1; ja-jp; T-01D Build/F0001) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1 NEWSAY connection: close accept-encoding: identity content-type: application/json; charset=utf-8 content-length: 172 ``` As you can see, the content-type is set to application/json with UTF-8 charset. However, the body contains hexadecimal data, not JSON. In the Mac version, Proxyman automatically handles this discrepancy and displays the data correctly. In the Windows version (2.19.0), the hexadecimal data is not fully displayed, and there's no option to decode it properly. Could you please investigate why the Windows version is unable to display the full hexadecimal content and why it lacks the automatic decoding feature present in the Mac version? ![img_v3_02i2_cc8e1c58-2f29-4015-9bc3-cf3336ee7c0g](https://github.com/user-attachments/assets/9321fb8d-e286-449d-80c1-5dcb903379e2)

kerem commented

2026-03-03 19:50:43 +03:00

Author

Owner

@kics223w1 commented on GitHub (Dec 31, 2024):

Yes we can. I will try to reproduce this issue and fix it.

@kics223w1 commented on GitHub (Dec 31, 2024): Yes we can. I will try to reproduce this issue and fix it.

kerem commented

2026-03-03 19:50:43 +03:00

Author

Owner

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

@aa1134665908 to work around this, please open the Raw Tab, select your text body -> Right Click -> Show as Base64.

It will decode your base64 string to JSON and auto prettify it

@NghiaTranUIT commented on GitHub (Dec 31, 2024): @aa1134665908 to work around this, please open the Raw Tab, select your text body -> Right Click -> Show as Base64. It will decode your base64 string to JSON and auto prettify it

kerem commented

2026-03-03 19:50:43 +03:00

Author

Owner

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

@kics223w1 it's a bug. If a body is a string, please show the body in the body too. Currently, it displays as a Hext in the Body Tab

@NghiaTranUIT commented on GitHub (Dec 31, 2024): @kics223w1 it's a bug. If a body is a string, please show the body in the body too. Currently, it displays as a Hext in the Body Tab

kerem commented

2026-03-03 19:50:43 +03:00

Author

Owner

@kics223w1 commented on GitHub (Dec 31, 2024):

Okay I will fix this.

@kics223w1 commented on GitHub (Dec 31, 2024): Okay I will fix this.