Currently, mitmproxy has a basic marking system (~marked filter and ~marker text matching), but there's no visual way to categorize or label requests in the mitmweb UI.
Instead of users relying on filter expressions for traffic organization, it'd be cool to retroactively categorize and label requests in the web UI. This is particular helpful if you're exploring a new site or app and don't necessarily know what your filter expressions would look like.
As a comparison I'm thinking this could be like burp suite organizer where a user can visually mark and track in a UI difference categories ("API", "Auth", "Crit Path", etc.).
Considerations and feature items for visual tagging in the UI:
- Displays user-assigned tags as color-coded badges next to each flow in the list
- Allows quick tag assignment via a UI button or context menu
- Filters flows by tag using existing filter syntax (
~marker or a new ~tag operator)
- Persists tags in flow metadata so they survive save/reload cycles
I'd be keen to PR this in, but wanted to check others want this or I'm missing the mark.
Currently, mitmproxy has a basic marking system (
~markedfilter and~markertext matching), but there's no visual way to categorize or label requests in the mitmweb UI.Instead of users relying on filter expressions for traffic organization, it'd be cool to retroactively categorize and label requests in the web UI. This is particular helpful if you're exploring a new site or app and don't necessarily know what your filter expressions would look like.
As a comparison I'm thinking this could be like burp suite organizer where a user can visually mark and track in a UI difference categories ("API", "Auth", "Crit Path", etc.).
Considerations and feature items for visual tagging in the UI:
~markeror a new~tagoperator)I'd be keen to PR this in, but wanted to check others want this or I'm missing the mark.