HAR export is not HAR 1.2 compliant (missing log.pages, some entries without response)

[habem86]

Description

When exporting traffic as HAR from Proxyman, the generated file is not fully compliant with the HAR 1.2 specification.
Because of this, some tools (Firefox Network Monitor and our in‑house HAR viewer) cannot open the file.

There are two issues:

1. log.pages is missing completely.
2. Some entries in log.entries do not contain a response object.

---

Steps to Reproduce

1. Start Proxyman.
2. Capture some HTTPS traffic.
3. Export the session as HAR.
4. Open the exported HAR file in Firefox Network Monitor (or another HAR viewer that expects HAR 1.2).

---

Current Behavior

• The exported HAR file has this structure at the top:

  {
    "log": {
      "version": "1.2",
      "creator": {
        "name": "Proxyman",
        "version": "3.5.0"
      },
      "entries": [
        {
          "startedDateTime": "2025-11-27T11:56:26+01:00",
          "time": 1948,
          "request": { ... }
          // in some entries there is no "response" object
        }
      ]
    }
  }

• There is no log.pages field.

• Some entries in log.entries are missing the response object (or it is null).

This causes errors in other tools, for example in Firefox:

Error while processing HAR file: can't access property "forEach", har.log.pages is undefined
Error while processing HAR file: can't access property "headers", entry.response is undefined

---

Expected Behavior

• log.pages should be present and be an array, for example:

  "pages": [
    {
      "startedDateTime": "2025-11-27T11:56:26+01:00",
      "id": "page_1",
      "title": "Proxyman export",
      "pageTimings": {}
    }
  ]

• Every entry in log.entries should contain a response object, even for failed/aborted requests, e.g.:

  "response": {
    "status": 0,
    "statusText": "",
    "httpVersion": "HTTP/1.1",
    "cookies": [],
    "headers": [],
    "content": {
      "size": 0,
      "mimeType": "",
      "text": ""
    },
    "redirectURL": "",
    "headersSize": -1,
    "bodySize": -1
  }

This would make the exported HAR files compatible with Firefox, Chrome DevTools and other HAR analyzers (including our internal viewer).

---

Environment

• App version: 3.5.0
• Windows/Linux version: Windows 11

---

[NghiaTranUIT]

Thanks, our team will check out and fix it @kics223w1