What each interception toggle does#

The settings menu has a block of checkboxes that change how the proxy treats traffic that flows through it.

HTTPS Interception#

When on, the proxy decrypts TLS traffic, so you can inspect and modify HTTPS requests. The machine that generates the traffic must trust the GraphDagger CA certificate. See Certificates.

When off, the proxy passes HTTPS connections through opaquely. You see the host and port that the client connected to. The request and response bodies stay encrypted, and you cannot read them.

System Proxy#

This toggle appears only when the capture source is Explicit Proxy. When on, GraphDagger reconfigures the host operating system at every recording start, so the system routes its traffic through the proxy. GraphDagger restores the previous setting when you stop the recording.

When off, you point clients at the proxy yourself.

Instrument#

When on, GraphDagger injects browser instrumentation into matching responses. The instrumentation powers the browser-confirmed edges in the network graph, and it gives the workspace richer per-request telemetry.

Some sites detect or sandbox the instrumentation. If you see odd behaviour on a specific page, turn this off and try again.

No Caching#

When on, the proxy strips cache-related headers from outgoing requests. Every request then reaches the origin instead of a stored response. This is the easiest way to confirm that a client calls the server you expect.

The toggle stays on until you change it. It does not reset between recordings.

Block Cookies#

When on, the proxy drops cookies from incoming requests. Use this to see a request without any session state, for example when you reproduce a logged-out flow.

The toggle stays on until you change it.