Nan vs requiem.http

Why You Need This: - Capture on TCP/IP layer, NOT system proxy. Avoid some applications not going through the proxy - Detect TLS connection and ALPN - Only capture and decrypt HTTPS the address you specify, to prevent certain applications from malfunctioning due to addresses that cannot be captured by packet capture. - Also support decrypt WebSocket How it works: - This app captures all IP packets (IP layer) - Next assemble into TCP stream (TCP layer) - Probe TLS connections and ALPN information to help you determine if there's any possibility of packet capture. - Next assemble into HTTPS/WebSocket packet (Application layer) if you MITM it

**Build Complete HTTP Requests** Start with a URL, then chain actions to add headers, a body, path segments, and query parameters. Each action modifies the request and passes it to the next — no scripting required. Compose complex API calls the same way you build any shortcut. **Send and See What Comes Back** Send requests and get syntax-highlighted responses. Methods, headers, status codes, and body content are color-coded. JSON is pretty-printed. Response timing tells you exactly how long each call takes. **Share Requests With a Link** Encode any request as a req.to URL — method, headers, body, everything. No server, no account. Anyone who opens the link sees the full request. Great for sharing API examples or debugging with teammates. **Standard Format** Requests are stored as .http files — the same plain-text format used by VS Code REST Client, JetBrains, and httpYac. Portable, readable, and not locked in a proprietary database. Read the spec at http-files.org.