Question 1

如何打开 HAR 文件？

Accepted Answer

在 Chrome、Edge 或 Firefox 中打开 DevTools，切换到 Network 面板，勾选 Preserve log，复现要抓取的页面或 API 流程，然后右键请求列表选择 Save all as HAR with content。把生成的 .har 文件拖到本工具，或使用文件选择器即可。全部在浏览器本地解析。In Chrome, Edge or Firefox open DevTools, switch to the Network tab, tick Preserve log, reproduce the page or API flow you want to capture, then right-click the request list and choose Save all as HAR with content. Drop the resulting .har file onto this tool, or use the file picker. Everything is parsed locally in your browser.

Question 2

把 HAR 文件上传到在线查看器安全吗？

Accepted Answer

通常不安全。HAR 是浏览会话的完整记录，包含你发出的每个请求头，Authorization bearer token、会话 cookie 和 API key 都以明文存在其中。本查看器不上传任何内容 — 文件由 File API 读取并在浏览器内解析 — 并且还能生成一份清空凭据的脱敏副本。Usually not. A HAR is a complete record of a browsing session and includes every request header you sent, so Authorization bearer tokens, session cookies and API keys sit inside it in plain text. This viewer never uploads anything - the file is read with the File API and parsed in your browser - and it can also produce a redacted copy with credentials stripped.

Question 3

瀑布图耗时分解代表什么？

Accepted Answer

每根柱状条展示单个请求的 HAR 各阶段：blocked 与 DNS 是排队和解析时间，connect 与 SSL 是 TCP 和 TLS 握手，send 是上传，wait 是服务端处理时间，receive 是下载。wait 过长通常说明服务端慢，receive 过长说明载荷大或网络慢。Each bar shows the HAR phases for one request: blocked and DNS are queue and lookup time, connect and SSL are the TCP and TLS handshakes, send is upload, wait is server think time, and receive is download. A long wait usually means slow server processing, while a long receive means a large payload or a slow connection.

Question 4

如何把请求复制为 cURL？

Accepted Answer

在请求列表中点击任意一行打开详情面板，切换到 Raw 标签并点 Copy cURL。该命令由抓取到的方法、URL、响应头和正文重建，可在终端、Postman 或 curl.exe 中重放这次调用。Click any row in the request list to open its detail panel, switch to the Raw tab, and press Copy cURL. The command is rebuilt from the captured method, URL, headers and body so you can replay the exact call in a terminal, Postman or curl.exe.

Question 5

分享前如何脱敏 HAR？

Accepted Answer

点 Redact and download，得到一份 Authorization 与 Cookie 响应头被清空、请求与响应正文被移除、敏感查询参数在 queryString 数组和 URL 中都被遮蔽的合法 HAR。结果仍能在任何 HAR 查看器中打开，可以安全附到 bug 报告或支持工单里。Press Redact and download to get a valid HAR with Authorization and Cookie headers emptied, request and response bodies removed, and sensitive query parameters masked in both the queryString array and the URL. The result still opens in any HAR viewer, so it is safe to attach to a bug report or a support ticket.