It would be very useful to have the ability to sort the requests list by different columns.
For example, users could sort requests by:
Path and Query
Host
Method
......
Ideally, clicking a column header would toggle between ascending and descending order.
This would make it much easier to analyze and organize a large number of requests, especially when working with HTTP Toolkit during debugging or security testing.
Example
For the Path and Query column:
/api/users?page=1
/api/users?page=2
/api/products
/login
The user should be able to click Path and Query to sort these requests alphabetically, and click it again to reverse the order.
The same functionality could be available for Host and other sortable columns.
Expected Behavior
Clicking a column header sorts the request list by that column.
Clicking it again reverses the sort order.
The currently active sort column and direction should be visually indicated.
Sorting should work with both textual and numerical columns where applicable.
This would significantly improve navigation and analysis when dealing with a large number of captured requests.
It would be very useful to have the ability to sort the requests list by different columns.
For example, users could sort requests by:
Path and Query
Host
Method
......
Ideally, clicking a column header would toggle between ascending and descending order.
This would make it much easier to analyze and organize a large number of requests, especially when working with HTTP Toolkit during debugging or security testing.
Example
For the Path and Query column:
/api/users?page=1
/api/users?page=2
/api/products
/login
The user should be able to click Path and Query to sort these requests alphabetically, and click it again to reverse the order.
The same functionality could be available for Host and other sortable columns.
Expected Behavior
Clicking a column header sorts the request list by that column.
Clicking it again reverses the sort order.
The currently active sort column and direction should be visually indicated.
Sorting should work with both textual and numerical columns where applicable.
This would significantly improve navigation and analysis when dealing with a large number of captured requests.