HAR — Multipart File Upload
A two-part multipart/form-data upload: a text file part with a fileName and a plain field part. The body uses CRLF between MIME parts because RFC 7578 requires it, even though the surrounding HAR document is LF-terminated — a distinction that matters when a replay tool rewrites the body.
{
"log": {
"version": "1.2",
"creator": {
"name": "Novus Examples HAR writer",
"version": "1.2",
"comment": "HAR 1.2 - de-facto format from an abandoned W3C editorial draft (2012); never published as a W3C Recommendation"
},
"browser": {
"name": "Sample Browser",
"version": "126.0"
},
"pages": [
{
"startedDateTime": "2026-08-07T09:14:22.031Z",
"id": "page_1",
"title": "https://www.example.com/cart",
"pageTimings": {
"onContentLoad": 214.5,
"onLoad": 388.9
}
}
],
"entries": [
{
"pageref": "page_1",
"startedDateTime": "2026-08-07T09:14:22.031Z",
"time": 137.7,
"request": {
"method": "POST",
"url": "https://api.example.com/v1/orders/o_20260807_0001/receipt",
"httpVersion": "HTTP/1.1",
"cookies": [],
"headers": [
{
"name": "Host",
"value": "api.example.com"
},
{
"name": "User-Agent",
"value": "Mozilla/5.0 (X11; Linux x86_64) NovusSampleAgent/1.0"
},
{
"name": "Content-Type",
"value": "multipart/form-data; boundary=----NovusSampleBoundary7MA4YWxkTrZu0gW"
},
{
"name": "Authorization",
"value": "Bearer SAMPLE-ACCESS-TOKEN-NOT-A-REAL-CREDENTIAL"
}Specifications
- Seed
- 61200
- Encoding
- UTF-8
- Line Endings
- LF
- Har Version
- 1.2
- Entries
- 1
- Post Mime Type
- multipart/form-data
- Parts
- 2
- Has File Name
- true
- Part Separator
- CRLF (required by RFC 7578)
- Spec Status
- HAR 1.2 - de-facto format from an abandoned W3C editorial draft (2012); never published as a W3C Recommendation
Testing contract
Expected to pass- Scenario
- Reconstruct a multipart upload from a capture and replay it.
- Expected result
- The boundary from the Content-Type header splits the body into exactly two parts, with the CRLF part separators preserved byte for byte.
What is a .har file?
HAR (HTTP Archive) is a JSON format that records a browser or client's network activity. A log object carries the creator, one or more pages, and an ordered list of entries, each holding a full request and response — method, URL, headers, cookies, query string, POST data, status, content, transfer sizes — plus per-phase timings for DNS, connect, send, wait, and receive. Every major browser's developer tools can export one.
How to use this file
Use an example .har file to test waterfall viewers, performance-budget checkers, and traffic-replay or mock-server tooling, asserting that entry timings sum to the recorded total and that header, cookie, and body content is parsed without loss.
How to use this file for testing
“HAR — Multipart File Upload” is a deterministic Novus Examples fixture for API testing, Performance testing, JSON parsing. OpenAPI/Swagger specs, GraphQL SDL, JSON Schema, paginated and problem+json error payloads, and webhook samples — for testing API clients, mock servers, contract tests, and schema validators.
Documented properties for this file: seed 61200 · 1 entries · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Test and coverage reports document their totals (suites, cases, passes, failures, skips, covered lines) in the spec table. Point your CI dashboard, coverage gate, or report converter at the file and assert those counts survive; format twins carry identical numbers so a conversion can be scored exactly.
Related files
- harHAR — Cache State Before and AfterA conditional request answered 304 with full beforeRequest and afterRequest cache state, next to a first-time fetch whose beforeRequest is null. The null is the documented way to say "not in the cache", and readers that treat it as a missing object rather than an explicit absence lose the distinction.
- harHAR — Cookie Set, Sent and ClearedA full session-cookie lifecycle: set at login, echoed on the next request, then expired at logout with Max-Age=0. Both the header and the parsed cookies array are present, and every value — including the form password field — is an obvious SAMPLE placeholder rather than a credential.
- harHAR — HTTP Error Responses (401 to 500)Five failing requests covering authentication, authorisation, a missing resource, rate limiting with a Retry-After header, and a server error that returns HTML instead of the JSON the client asked for. The last one is the case that breaks clients which parse by status code rather than by content type.
- harHAR — HTTP/2 Request with Connection DetailAn HTTP/2 entry with lowercase pseudo-headers, an httpVersion of "h2" rather than "HTTP/2.0", an ssl phase inside connect, and three underscore-prefixed custom fields. Version strings are not standardised across writers, so anything matching on "HTTP/1.1" misses this entry entirely.
- harHAR — JSON API Session (GET, POST, PUT, DELETE)A four-call REST session against a fictional API host, with JSON request bodies in postData, an Authorization header carrying an obvious SAMPLE placeholder token, and a 204 response that has no body at all. The right shape for testing a HAR-to-mock-server or HAR-to-code converter.
- harHAR — Page-Load Waterfall (5 Requests)A five-request page load — document, stylesheet, script, image and favicon — across two fictional hosts, with full per-phase timings and an onLoad page timing. Every entry's time equals the sum of its non-negative timing phases, so a waterfall renderer can be checked arithmetically rather than by eye.
Generated by generation/testing.py. Free for any use, no attribution required — license.