[GH-ISSUE #680] More detailed request and response info #679

Open
opened 2026-03-03 19:20:53 +03:00 by kerem · 10 comments
Owner

Originally created by @pokryfka on GitHub (Nov 5, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/680

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version

2.11.1 (21110)

macOS Version

10.15.7 (19H2)

Feature request

The application is great and UX is much nicer than (Java) Charles Proxy.
However request and response information is limited.

Please show more detailed request and response information (details below).

This should probably be split into a few issues (requests).
Personally I find especially useful to know when client started to receive response;
I think at the moment Duration includes time to send the request, waiting for server response and then downloading it.

Timing

  • request start/end time
  • response start/end time

less important but useful:

  • DNS
  • connect
  • TLS handshake

Size

  • request size
  • uncompressed body size (if compressed) - have not tested yet if Proxyman can uncompress it

Connection

  • remote address (ip)
  • remote port

TLS

  • server certificate details including expiration date
Originally created by @pokryfka on GitHub (Nov 5, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/680 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version 2.11.1 (21110) ### macOS Version 10.15.7 (19H2) ### Feature request The application is great and UX is much nicer than (Java) Charles Proxy. However request and response information is limited. Please show more detailed request and response information (details below). This should probably be split into a few issues (requests). Personally I find especially useful to know when client started to receive response; I think at the moment Duration includes time to send the request, waiting for server response and then downloading it. #### Timing - request start/end time - response start/end time less important but useful: - DNS - connect - TLS handshake #### Size - request size - uncompressed body size (if compressed) - have not tested yet if Proxyman can uncompress it #### Connection - remote address (ip) - remote port #### TLS - server certificate details including expiration date
Author
Owner

@pokryfka commented on GitHub (Nov 5, 2020):

For reference Request overview in Charles Proxy:

charles
<!-- gh-comment-id:722383259 --> @pokryfka commented on GitHub (Nov 5, 2020): For reference Request overview in Charles Proxy: <img width="711" alt="charles" src="https://user-images.githubusercontent.com/5090827/98247929-38f12e00-1faf-11eb-9492-eb108348f090.png">
Author
Owner

@NghiaTranUIT commented on GitHub (Nov 5, 2020):

Thanks for the rise 👍 .

  • It will show some useful information (not all like Charles) on the Summary Tab (Next to Raw Tab).
  • I will select important values (Request Start, Request End, TLS Version, DNS,...) to show on the Main Table (Right click on the Column to select the visible columns). Therefore, it's easier to compare with other request
Screen Shot 2020-11-05 at 20 41 01
<!-- gh-comment-id:722385179 --> @NghiaTranUIT commented on GitHub (Nov 5, 2020): Thanks for the rise 👍 . - It will show **some** useful information (not all like Charles) on the Summary Tab (Next to Raw Tab). - I will select important values (Request Start, Request End, TLS Version, DNS,...) to show on the Main Table (Right click on the Column to select the visible columns). Therefore, it's easier to compare with other request <img width="353" alt="Screen Shot 2020-11-05 at 20 41 01" src="https://user-images.githubusercontent.com/5878421/98248224-3b4f8a00-1fa7-11eb-83b9-a68585cb4aa8.png">
Author
Owner

@pokryfka commented on GitHub (Nov 5, 2020):

Awesome, thank you for prompt response.

Request Start/End, and Response Start/End would be great to have.

<!-- gh-comment-id:722388056 --> @pokryfka commented on GitHub (Nov 5, 2020): Awesome, thank you for prompt response. Request Start/End, and Response Start/End would be great to have.
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 19, 2020):

@pokryfka Good news that this feature is supported 🎉

Let check out this BETA: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.14.2_Feature_Summary.dmg

CleanShot_2020-12-19_at_15_57_21_2x
<!-- gh-comment-id:748445172 --> @NghiaTranUIT commented on GitHub (Dec 19, 2020): @pokryfka Good news that this feature is supported 🎉 Let check out this BETA: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.14.2_Feature_Summary.dmg <img width="1671" alt="CleanShot_2020-12-19_at_15_57_21_2x" src="https://user-images.githubusercontent.com/5878421/102685424-04f66300-4213-11eb-8852-829c9a2fcfee.png">
Author
Owner

@pokryfka commented on GitHub (Dec 20, 2020):

Looking good, thank you!

I will try to test with endpoint which takes a bit more time to process request.

<!-- gh-comment-id:748546067 --> @pokryfka commented on GitHub (Dec 20, 2020): Looking good, thank you! I will try to test with endpoint which takes a bit more time to process request.
Author
Owner

@john-webb commented on GitHub (Sep 18, 2024):

+1 to the detailed request breakdown. Helpful when optimizing requests.

  • DNS
  • Connect
  • TLS handshake
<!-- gh-comment-id:2358885102 --> @john-webb commented on GitHub (Sep 18, 2024): +1 to the detailed request breakdown. Helpful when optimizing requests. - DNS - Connect - TLS handshake
Author
Owner

@NghiaTranUIT commented on GitHub (Sep 19, 2024):

@john-webb May I ask if you mean the timing or the info of the DNS, Connect, and TLS handshake?

<!-- gh-comment-id:2359703438 --> @NghiaTranUIT commented on GitHub (Sep 19, 2024): @john-webb May I ask if you mean the timing or the info of the DNS, Connect, and TLS handshake?
Author
Owner

@john-webb commented on GitHub (Sep 19, 2024):

Thanks for quick response. I mean the timing of each of those steps. Similar to the Charles screenshot above in the expanded timing section.

<!-- gh-comment-id:2360939600 --> @john-webb commented on GitHub (Sep 19, 2024): Thanks for quick response. I mean the timing of each of those steps. Similar to the Charles screenshot above in the expanded timing section.
Author
Owner

@cgomez-rb commented on GitHub (Sep 30, 2024):

Just now I came up with a use case where we need the timing for DNS, TLS, Connect, etc... it would be great to have it in Proxyman.

<!-- gh-comment-id:2384387342 --> @cgomez-rb commented on GitHub (Sep 30, 2024): Just now I came up with a use case where we need the timing for DNS, TLS, Connect, etc... it would be great to have it in Proxyman.
Author
Owner

@NghiaTranUIT commented on GitHub (Oct 1, 2024):

Thanks, I will support it 👍

<!-- gh-comment-id:2384598318 --> @NghiaTranUIT commented on GitHub (Oct 1, 2024): Thanks, I will support it 👍
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#679
No description provided.