-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please support exporting network logs via proxyman-cli #2180
Comments
@ponienchen please use this Beta build https://download.proxyman.io/beta/Proxyman_5.10.0_Support_export-log_in_the_proxyman-cli.dmg
/Applications/Proxyman.app/Contents/MacOS/proxyman-cli export-log -m all -o "~/desktop/all"
Export certain domains (Only Host, no scheme, no port, no paths, and no Query)
/Applications/Proxyman.app/Contents/MacOS/proxyman-cli export-log -m domains -o "~/desktop/twitterlog" --domains 'api.twitter.com' --domains 'www.producthunt.com You can find the example command line at https://docs.proxyman.io/command-line#export-proxyman-log |
Thank you so much Noah!
I will check it out!
Peter
…On Sat, Nov 2, 2024 at 7:36 AM Noah Tran ***@***.***> wrote:
@ponienchen <https://github.com/ponienchen> please use this Beta build
https://download.proxyman.io/beta/Proxyman_5.10.0_Support_export-log_in_the_proxyman-cli.dmg
- Export all (ProxymanSession)
/Applications/Proxyman.app/Contents/MacOS/proxyman-cli export-log -m all -o "~/desktop/all"
Export certain domains (Only Host, no scheme, no port, no paths, and no Query)
- Export certain domains
/Applications/Proxyman.app/Contents/MacOS/proxyman-cli export-log -m domains -o "~/desktop/twitterlog" --domains 'api.twitter.com' --domains 'www.producthunt.com
You can find the example command line at
https://docs.proxyman.io/command-line#export-proxyman-log
—
Reply to this email directly, view it on GitHub
<#2180 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFCSYG77L3BVZ5PDKBHUELZ6TPOZAVCNFSM6AAAAABQ4XLCV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGAYTAMRUGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
hi, @NghiaTranUIT The output is a binary file. Also, is it possible to allow for specifying path ? And can we be allowed to specify the query |
These files can be opened by Proxyman app. If you want to open it as a JSON: -> Rename to zip -> Unzip -> Bunch of JSON
Not yet, this version only works with domain and all mode |
Thank you, @NghiaTranUIT The bodyData is encrypted for both request and response, and so I am not able to use this data. Can we by default show encrypted bodyData, but add a flag to optionally show decrypted bodyData for both request & response ? |
It's not encrypted. It's encoded as a Base64 string. You should decode it to to JSON or binary data. |
Thanks for the info on the base64 encoding, @NghiaTranUIT |
Hi, @NghiaTranUIT |
I will play with this for a few days and if I see any issues, I will report it here. |
Hi, @NghiaTranUIT Question. |
It's available in both versions. I will release this update on the next release 👍 |
Thank you, @NghiaTranUIT |
Appreciated you working on this feature! |
Description
In one of my automation suites, I would like the ability to export the network logs via proxyman-cli in order to check something.
Why this feature/change is important?
Some of my tests are making some api calls to report user interactions with the app, and it will be helpful to be able to test the payload of those calls as part of the automation.
Please support this use case.
Thank you so very much.
The text was updated successfully, but these errors were encountered: