Introducing Agents.·Read
OverviewAgentsWorkflowsExecutionDeveloper ToolsSecurityLibrary

Utilities

Turn saved HTTP flows into a HAR file

Convert an existing HTTP flow capture to a native HAR file.

Agent
Inspect saved request and response recordsMove HTTP capture data between file-processing nodesExport without replaying traffic

overview

What mitmproxy-export does

Supply a saved mitmproxy HTTP flow FILE. The wrapper runs mitmdump with its proxy server disabled, reads the local capture and writes the native HAR 1.2 artifact. It does not open a proxy listener or replay requests.

The HAR includes captured HTTP headers and bodies. Export is a format conversion, not redaction: the output retains the capture data that the native exporter includes. It is distinct from decoding packets from a PCAP.

Input must be a nonempty regular, nonsymlink file of at most 50 MiB. The native subprocess has a 90-second timeout, a 2 GiB address-space limit and a 100 MiB per-file size limit. These subprocess limits are not a total-container resource guarantee. The output path must not exist. At least one exportable HTTP flow is required.

source hub.docker.com/r/nenadzaric/skills-intel-mitmproxy-export

use cases

Where mitmproxy-export fits

Inspect saved request and response records

Read native HAR request/response fields from an existing HTTP flow file. The owned saved-run fixture exports one GET request and its HTTP 201 response.

Move HTTP capture data between file-processing nodes

Use the HAR file as an artifact for a downstream parser. The native output includes headers, bodies and timings rather than a replacement summary.

Export without replaying traffic

Work from a supplied native flow capture. Proxy listening, replay, addons and custom configuration are not exposed.

reference

mitmproxy-export inputs and flags

1 inputs
NameTypeFlagDescription
inputFILE--inputSaved mitmproxy native flow file, max 50 MiB, containing HTTP flows. Output includes captured headers and bodies.

Showing key inputs. mitmproxy-export exposes 1 inputs in total.

example

Run mitmproxy-export

mitmproxy-export · command
python3 /app/run.py --input saved.flow result.har
sample output
                "response": {
                    "status": 201,
                    "statusText": "Created",
                    "httpVersion": "HTTP/1.1",

guidance

Choosing mitmproxy-export

Choose this node for saved mitmproxy HTTP flows and a HAR artifact. Packet captures require a packet decoder such as the upstream TShark CLI; they are a different input format.

TShark (upstream CLI)

Decode a packet capture into protocol fields rather than export saved mitmproxy HTTP flows as HAR.

faq

mitmproxy-export questions

No. The fixed mitmdump command disables the proxy server and reads an existing local flow file. No replay operation or remote target input is exposed.

This job requires a native mitmproxy flow file with exportable HTTP flows. A packet decoder such as the upstream TShark CLI reads PCAP; protocol JSON and HAR are different formats.

No. Captured headers and bodies remain part of the native export. This node does not provide a redaction stage.

Input must be a nonempty regular, nonsymlink file of at most 50 MiB. The native subprocess has a 90-second timeout, a 2 GiB address-space limit and a 100 MiB per-file size limit. These subprocess limits are not a total-container resource guarantee. The output path must not exist. At least one exportable HTTP flow is required. Native failure becomes adapter exit 2, with bounded diagnostics. Empty or non-HTTP-only exports are rejected, and existing output is preserved.

The tested pin is mitmproxy 12.2.3. The existing owned synthetic platform run has a downloaded passed verifier and native HAR. Runtime adapter bytes match the preserved source, public image and source/notices downloads have been verified anonymously, and the original tool ID is public in the Library. This is reused execution proof, not a newly run capture.

The source link provides immutable ORAS retrieval directions and a bundle SHA-256 for the actual wrapper, Dockerfile, fixtures and saved proof, original runtime notices, corresponding Debian sources and patches, and collected Python and embedded component source. The upstream project uses MIT terms with original component licenses retained. No reproducible-build or security-clearance claim is made.

related

More Utilities tools

  1. browser-fetch

    Headless Chromium render: requested URL, final URL, status, and title next to the page.

  2. cewl

    Spider a URL and return a wordlist for password crackers.

  3. csvkit

    SQL on one CSV. The table name is the file stem.

  4. dnsgen

    Wordlist and mined-word subdomain permutation.

  5. duckdb

    In-process SQL on CSV, JSON, and Parquet. No server.

  6. edge-tts

    Microsoft Edge neural speech from text or a script file. No API key.

Run mitmproxy-export yourself

Verbatim response-header excerpt from native HAR downloaded from the existing owned synthetic run. It is not a complete HAR document. The full saved artifact contains the request, response body and timings.

Open mitmproxy-export in the libraryBuild a workflow with it

Facts on this page come from the live Trickest tool library.