HTTP Traffic Export options in Fiddler

I've been taking notes from Eric Lawrence's recorded presentation at MIX10 on Fiddler for future reference. This is the fourth part, check the earlier three tips if you haven't already read them -

• Track HTTP traffic in Firefox with FiddlerHook
• FiddlerCap makes HTTP Traffic Capture easier
• 6 ways to filter HTTP traffic with Fiddler

To share HTTP traffic debugging information, Fiddler offers 10 ways to export HTTP traffic -

1. Copy sessions to the clipboard - right-click & copy headers, URL or entire session info
2. Store as a plain-text file
3. Extract binary response bodies
4. Archive to a database
5. Export a Visual Studio .WebTest file - Visual Studio Web Test is a Visual Studio Team System feature that allows playback
6. Write your own - fully scriptable, so you can write your own exporters
7. Fiddler's native "Session Archive ZIP" (SAZ) format
8. HTTP Archive JSON (v1.1 & v1.2) - The two HTTP Archive JSON formats (*.har) are supported by a growing list of open-source and commercial tools and web services.
9. WCAT Load Test Script - Microsoft Web Capacity Analysis Tool (WCAT) can simulate thousands of concurrent users making requests to a single web site or multiple web sites. A script exported from Fiddler can be loaded in WCAT & previously-captured requests can be replayed for functional-testing and load-testing purposes.
10. Raw Files - this export format allows you to easily dump captured response files to a folder on disk; this allows you to easily collect audio, video, or image files for instance.

The last 3 “out of the box” options in the above list were mentioned by Eric in a recent blog post.

The introduction of HTTP Archive spec (*.har) support means than you can run an archive file generated by Fiddler in Firebug or similar tools like HTTPWatch,  and vice versa. As Steve Souders says,

With the adoption of HAR ..., we’re moving to having a record of the page load experience that can be saved and shared, and performance analysis that is consistent regardless of what browser and development environment you work in.

180