HttpWatch supports a number of different file formats for saving the results from a recorded session. The choice of file format depends on the features and interoperability you require with other platforms and tools.
This is the default file format used by HttpWatch to save and load log files. If you are only going to open the log files in HttpWatch Studio or use them through automation this is the preferred format for the following reasons:
The HTTP Archive format uses JSON and was originally designed by collaboration between the HttpWatch and Mozilla development teams. It is now supported in all major browsers and most network monitoring tools. It therefore offers interchange between many different platforms and tools. The data within the file can be easily accessed using the JSON support available in most programming languages. The downsides of this format compared to HWL are:
Also, there are some significant differences in the HAR implement across tools and browsers that sometimes prevents a HAR file from being loaded in one tool after being recorded in another.
The CSV export format can be customized to contain almost any data field displayed by HttpWatch or can simply be based on the columns selected for display in the main request grid. The format is useful if you just want to view certain data items in Excel or have a simpler file format to import into other tools.
HttpWatch log files cannot re e-loaded from CSV.