You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hard to determine what routes belong to what, you have to manually organize them which is a time sink and can lead to confusion in large APIs/projects.
Proposal
Mitmproxy should have a directory sidebar similar to the one in Charles, and then the ability to easily export/import it retaining the structure in folders.
This way it's easy to tell where everything is in the API at a simple glance.
This feature would not only make working with APIs easier but also really help mitmproxy stand out among its competitors. Since Charles is the only proxy client to date to offer this feature but is locked behind a subscription/proprietary code.
Alternatives
N/a
Additional context
N/a
The text was updated successfully, but these errors were encountered:
So basically #5627 but for mitmproxy instead of mitmweb?
I'm not sure this type of UI can be easily navigated in a terminal. But feel free to submit a PoC PR!
Prinzhorn
changed the title
[Proposal]
Site map/tree view for mitmproxy
Feb 15, 2024
Problem Description
Hard to determine what routes belong to what, you have to manually organize them which is a time sink and can lead to confusion in large APIs/projects.
Proposal
Mitmproxy should have a directory sidebar similar to the one in Charles, and then the ability to easily export/import it retaining the structure in folders.
Example here:
https://deliveroo.engineering/images/posts/how-to-use-charles-proxy-to-rewrite-https-traffic-for-web-applications/02-after.png
This way it's easy to tell where everything is in the API at a simple glance.
This feature would not only make working with APIs easier but also really help mitmproxy stand out among its competitors. Since Charles is the only proxy client to date to offer this feature but is locked behind a subscription/proprietary code.
Alternatives
N/a
Additional context
N/a
The text was updated successfully, but these errors were encountered: