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
Site map/tree view for mitmproxy #6662
Labels
kind/feature
New features / enhancements
Comments
So basically #5627 but for mitmproxy instead of mitmweb? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: