Description
After running a request, it would be useful to export the request/response pair as an HTTP Archive (HAR 1.2) file from the response pane.
HAR is the standard interchange format for HTTP traffic — an exported file can be opened in Chrome/Firefox DevTools, shared with teammates or API vendors when reporting issues, and consumed by a wide range of analysis and replay tooling.
This complements #1636, which requests HAR import; export was also requested in the comments there (e.g. #1636 (comment) — "exporting to a HAR file would also be great").
The export should reflect the request as it was actually sent (interpolated URL, resolved auth headers, serialized body) rather than the pre-interpolation template, so the file is a faithful record of the wire traffic.
I have an implementation ready in #8484.
🤖 Generated with Claude Code
Description
After running a request, it would be useful to export the request/response pair as an HTTP Archive (HAR 1.2) file from the response pane.
HAR is the standard interchange format for HTTP traffic — an exported file can be opened in Chrome/Firefox DevTools, shared with teammates or API vendors when reporting issues, and consumed by a wide range of analysis and replay tooling.
This complements #1636, which requests HAR import; export was also requested in the comments there (e.g. #1636 (comment) — "exporting to a HAR file would also be great").
The export should reflect the request as it was actually sent (interpolated URL, resolved auth headers, serialized body) rather than the pre-interpolation template, so the file is a faithful record of the wire traffic.
I have an implementation ready in #8484.
🤖 Generated with Claude Code