GROUPING The session list no longer has to be one long run of requests in the order they arrived. A control above the list switches between three arrangements: • Time — every request in capture order, as before • Host — one collapsible group per host • Domain — a tree of domain, then host, then path folders, then the requests themselves Nothing is reordered: a group is still that host's traffic in the order it happened. Collapse state is kept when you switch. Subdomains fold under their registrable domain, so api.example.com and cdn.example.com sit together under example.com. REVERSE PROXY Reverse proxy rules now capture. Forward a local port to an upstream server and every request across it appears in the session list like any other, with full headers, bodies and timing. Rules can add or remove request headers, add response headers, and rewrite path prefixes. This is the way in when you cannot change a client's proxy settings or install a certificate on it: point the client at 127.0.0.1 instead. FIXES • The response body pane could show the previously selected request's body under the newly selected request's URL. It shows the right one. • Exported sessions now come back exactly as they went out. Images and other binary bodies survive instead of being dropped, JSON is no longer silently reformatted, and timings, TLS details and session identity are all carried. Reopening a file you already have no longer duplicates it. • A failed export said nothing and looked like it had worked. It reports. • A TLS handshake the client abandoned was always reported as "the client does not trust the FlowProxy CA", even when the CA was installed and working. Handshake failures now say what actually happened; a browser blocking a tracker is no longer described as a certificate problem. • Long captures stay within their memory budget. A sustained capture could grow well past it and push the machine into swap. • A rule whose port was already in use reported success and then quietly did nothing.