mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #110] Proposed improvements. #108
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dreadlocked on GitHub (Apr 8, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/110
Originally assigned to: @NghiaTranUIT on GitHub.
First and foremost, I love this project, made in native languages, it's super fast and lightweight
, for real, thanks you so much for creating this project. Keep on it!!!
I'm a hardcore proxy software user for web applications security analysis. I just wanted to propose some features or user interfaces features which me (and many people I think) would love to have:
Sadly I'm not a good C++/Swift programmer, if it were, I would implement those features myself. Again, I love this project, please, do not give up!
Edit: It would also be great to make this project open source, I think many people could be interested on improve this project.
@NghiaTranUIT commented on GitHub (Apr 9, 2019):
Thank for kind word @dreadlocked, your proposal is the motivation to help me improve Proxyman 🥇
Regarding
Thank you for the detail proposal. Let me know if you need to discuss in detail 👍
@duraki commented on GitHub (Apr 11, 2019):
+1 for
Qucik Repeat! 😍 Can't wait for plugins tbh.@NghiaTranUIT commented on GitHub (Apr 21, 2019):
Hey @dreadlocked,
I've released the Proxyman 1.3.6, in this version, I add a small tweak in Compose windows (Screenshot), so you can keep the windows and send the request many time you like without losing your edit.
This could help you for the first check in your proposal 👍
Thank you in advance 🌟
@dreadlocked commented on GitHub (Apr 22, 2019):
Hi! It's cool to see that you are improving the UI/UX, nice work! For this point I was thinking on something like this https://imgur.com/a/K8O7kBb (I made a bit of photoshop :D). A split panel. When you click Send, the response appears on the second panel, then you can modify your request again and click send, and the response appears again on the second panel.
This way I can modify a single request as many times as I want without many clicks.
During a web application analysis, when testing an endpoint for bugs, or unexpected behaviours, lot of requests are done testing different things on the same endpoint, for example, changing the value of a numeric parameter for a string, changing a single value for an array, changing request headers... etc So it's critical to have a way to repeat a request multiple times without having to "Click Send (panel closes) > Click on the new generated response to see the response > Right click on Edit and Repeat ... > Edit query a bit > Click send ...".
@joanbono commented on GitHub (Apr 22, 2019):
That would be AMAZING
@NghiaTranUIT commented on GitHub (Apr 23, 2019):
Thank for elaborate feedback @dreadlocked, I agree that by this way, you can boost the productivity more than just closing and edit again. I will take it into account in next builds 👍
@dreadlocked commented on GitHub (Jun 2, 2019):
When debugging an app which has a lot of requests per second (many of them) It's really hard to find the response when "Edit and resend" is used. I'm having this issue since I'm using Proxyman. On other traffic analysis apps such as Burp Suite, when you "Edit and resend" a request, the response is show besides the request, ZAP Proxy does this way too.
It's easier to work with the response spawning on a "window" or section besides the request and being able to edit and resend the same request as much times as you want, than "Edit and resend", then looking where the response is (usually at the bottom, but when the application does many request on background, such as web apps, this will nearly never happen), then looking the response body and then Edit and resend again.
Time ago I did a "proof of concept" of how this beside response section could look, based on Burp Suite and ZAP Proxy UI: https://imgur.com/a/K8O7kBb
Thanks in advance!