[GH-ISSUE #1958] Long numbers in json truncated till 12s sign #1949

Open
opened 2026-03-03 19:55:43 +03:00 by kerem · 5 comments
Owner

Originally created by @VolodymyrPavlyshenOnseo on GitHub (Mar 6, 2024).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1958

Hello there, I a have an issues with numbers in requests displaying (and sending in proxy) , my work require exact accuracy, so numbers need to be calculated till the last sign (sometimes it is 25 or 30 signs) as I can see proxy round it till 11 or 12s sign, is it expected/ limitation or a bug?
For example proxyman displays 77.52551806700806 in request same time as it should be 77.52551806700806505198504

Originally created by @VolodymyrPavlyshenOnseo on GitHub (Mar 6, 2024). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1958 Hello there, I a have an issues with numbers in requests displaying (and sending in proxy) , my work require exact accuracy, so numbers need to be calculated till the last sign (sometimes it is 25 or 30 signs) as I can see proxy round it till 11 or 12s sign, is it expected/ limitation or a bug? For example proxyman displays 77.52551806700806 in request same time as it should be 77.52551806700806505198504
Author
Owner

@NghiaTranUIT commented on GitHub (Mar 6, 2024):

Can you show me the screenshot @VolodymyrPavlyshenOnseo

and may I ask If you're using any debugging tools ? (Map Local, Breakpoint or Scripting) 🤔

<!-- gh-comment-id:1981131175 --> @NghiaTranUIT commented on GitHub (Mar 6, 2024): Can you show me the screenshot @VolodymyrPavlyshenOnseo and may I ask If you're using any debugging tools ? (Map Local, Breakpoint or Scripting) 🤔
Author
Owner

@VolodymyrPavlyshenOnseo commented on GitHub (Mar 6, 2024):

none of them, also tried same request on Charles, works fine
What screenshot do you need?

<!-- gh-comment-id:1981147200 --> @VolodymyrPavlyshenOnseo commented on GitHub (Mar 6, 2024): none of them, also tried same request on Charles, works fine What screenshot do you need?
Author
Owner

@NghiaTranUIT commented on GitHub (Mar 6, 2024):

if you're using the Body or Raw Tab, it will show exactly how the JSON is. It doesn't modify it.

If we use JSON TreeView, it might be a case because it converts to NSDictionary to perform the JSON View.

Which tab do you use?

<!-- gh-comment-id:1981153404 --> @NghiaTranUIT commented on GitHub (Mar 6, 2024): if you're using the Body or Raw Tab, it will show exactly how the JSON is. It doesn't modify it. If we use JSON TreeView, it might be a case because it converts to NSDictionary to perform the JSON View. Which tab do you use?
Author
Owner

@NghiaTranUIT commented on GitHub (Mar 6, 2024):

Or share with me the cURL, you can put your 12-digit number as a JSON body, and share it with me. I'd like to reproduce it

<!-- gh-comment-id:1981155451 --> @NghiaTranUIT commented on GitHub (Mar 6, 2024): Or share with me the cURL, you can put your 12-digit number as a JSON body, and share it with me. I'd like to reproduce it
Author
Owner

@VolodymyrPavlyshenOnseo commented on GitHub (Mar 6, 2024):

ah I can see, in Body tab it is truncated in tree - rounded, but in raw it is fully correct, thank you

<!-- gh-comment-id:1981160300 --> @VolodymyrPavlyshenOnseo commented on GitHub (Mar 6, 2024): ah I can see, in Body tab it is truncated in tree - rounded, but in raw it is fully correct, thank you
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#1949
No description provided.