This document is intended to describe structure ofa HTTP Archive file (*.har) that should be used when exporting data from Firebug Net panel. The current version of the format isn't finalized and is open for further proposals.

This is sexy. I hope this gets adopted. Importing HTTP capture data from all the different tools is a pain in the ass. The best I've found is Web Scarab, which can export/store captured HTTP traffic requests and responses as simple flat files with the raw HTTP. Many of the capturing proxies and web security tools have flaky export as best, or export into a encrypted, undocumented format (*cough*SPIProxy*cough*). The ones that do export to a plain text typically fail on binary responses or gzipped responses as soon as they hit an unprintable ASCII character. Of the few remaining many will export a normalized version of the response, where GZIP is undone and responses are dechunked and HTTP header order has been normalized.

Need to look at this more. Already see some potential issues and have some questions about this JSON format.

-Is order preserved? headers? postdata? query strings?
-What about nameless/valueless params? (http://site.com/foo/php?sorted&grouped)
-Multiple forms in post data?