Overwork the tab concept and introduce a real request history

In my opinion the current concept of different component tabs (Spider, AJAX 
Spider, Fuzzer, Active Scan, etc.) is a little bit confusing and holds back 
some useful information at the moment.

Example:
When a Spider scan is started, the Spider tab is opened and the different found 
sites are added to its table. The table displays the columns "Processed", 
"Method", "URI" and "Flags". These information are expected and helpful of 
course.
But what is about the details of the requests?
At the moment it is neither possible to see the request nor the response of the 
table entries itself. Also the other information which are provided by the 
History tab (Id, Req. Timestamp, Method, URL, Code, Reason, TRR, Size Resp. 
Body, Highest Alert, Note, Tags) are missing.

In my opinion these information should be available for all requests regardless 
of the component.

Therefore I would suggest the following:

Each component tab displays its own custom table containing its specific needed 
information.
Additionally there is the History tab which contains all requests from all 
available components displaying all common information mentioned above.

So this means that all requests are centralized in the History tab (a real 
request history) and can be controlled by the filter of the History tab (e.g. 
new filter "category").

In order that functionality of the current History tab is not lost, a new tab 
named "Proxy" (or something like that) is added. This one contains all manual 
and proxied requests and also displays a custom table like the other tabs.

This way information are provide clearly and in consistent way through the 
whole application.

Original issue reported on code.google.com by marabic...@gmail.com on 13 May 2015 at 12:18

ashenchowthee / zaproxy

Overwork the tab concept and introduce a real request history #1635