Skip to content
Casazium
Casazium

Import and export (HAR) ​

HAR is the format browsers' developer tools use to save network traffic. Wirescry reads and writes it, so you can share a capture, attach one to a bug report, or look at a HAR file someone sent you.

Export ​

File → Export HAR… (⌘/Ctrl+S), or Export HAR above the list, saves what the list shows: with a quick filter or search active, only the matching requests, in list order. To export everything, clear the search and choose All. At most 10,000 requests go in one file.

  • Bodies are saved decoded, up to 50 MB each; a longer body is cut and the entry says so in its comment. Text is saved as is, anything else as base64.
  • WebSocket connections are saved with their messages, in the same form Chrome uses (_webSocketMessages).
  • Failures are saved as _error (the field browsers use) and _wirescryFailure (the kind, code and explanation), and the Pro rule that handled a request as _wirescryRule.
  • Requests from before a proxy restart are left out, because their details were lost; Wirescry tells you how many.

WARNING

A HAR file holds everything in the requests you export: cookies, authorization headers, tokens and bodies. Check it, or narrow the export with a search, before you share it.

Import ​

File → Import HAR… (⌘/Ctrl+O) takes a .har or .json file of up to 256 MB, from Wirescry, a browser or another tool. Its requests join the list, marked with a HAR badge and "Imported from" in their details, and work like captured ones: search them, read their bodies, export them again.

  • At most 10,000 entries are read. Imported requests count toward the list's 10,000; if they don't fit, the oldest requests leave the list, and Wirescry says how many.
  • http, https, ws and wss entries are read. Entries such as data: and chrome-extension: URLs are skipped.
  • Entries Wirescry can't read are skipped; it reports how many, and why for the first few.
  • Bodies are taken as given. An entry with no response is listed as failed: "No response in the HAR file".
  • WebSocket messages are read from Chrome's _webSocketMessages, and failures from _wirescryFailure or _error.