Practical constraints to set expectations—some are performance tradeoffs, others are platform realities (pinning, sandboxes).
Evaluation builds may enforce a time‑limited trial stored locally. Trial checks are not a cryptographic license server—treat them as a convenience gate for honest evaluation, not fraud‑proof enforcement.
Apps that pin certificates or public keys may fail through any MITM proxy unless you use a debug build without pinning. This is not a ProxyHawk bug.
For performance, live list updates may send a compact JSON payload (truncated bodies, subset of headers). The canonical full request/response lives in the capture store; the detail pane and get entry APIs resolve the complete data when possible. If an entry was evicted from the store, detail may be incomplete.
Very large uploads/downloads may be truncated for display or for callback payload size. Extremely large bodies may be handled specially in the UI (preview only).
On macOS, the API Client may execute via system curl for TLS parity. Behavior can differ from in‑app Rust networking or from a mobile device’s stack—compare captures when debugging TLS issues.
Desktop builds may run with broad filesystem access relative to a fully sandboxed Mac App Store app—appropriate for a developer tool, but it increases local blast radius if malware runs as your user. Follow Security & privacy.
Automatic system proxy toggles depend on macOS permissions and helper installation. If the helper is not approved, use manual proxy settings in Wi‑Fi or per‑app configuration.
