What mapping redirects#

Mapping redirects a URL to a different destination. Two flavours sit side by side as their own sub-tabs.

• Map Remote: redirect a host or URL to another host on the network.
• Map Local: serve a URL from a directory on your machine.

How mapping is different from rules#

A rule modifies a request as it passes through. A mapping rewrites the destination entirely: matching traffic goes somewhere else.

Use mapping when:

• You want to swap a production API for staging without touching the client.
• You want to iterate on a local asset without redeploying.
• You want to point a mobile build at a dev backend without changing its code.

For everything else (header rewrites, status replacements, content edits), use a rule.

Where mappings live#

GraphDagger stores mappings alongside rules in the rules store. Mappings apply to live recording only, so a static HAR file does not redirect anything.

What every mapping row holds#

Both Map Remote and Map Local list one rule per row. Every row has the same shape.

• Toggle: enables or disables the rule without a delete.
• Fields: the values that define the mapping.
• Actions: a regex toggle (Map Remote only), a test button, and a delete button.

Test a mapping first#

Both Map Remote and Map Local have a built-in test feature so you can verify a mapping without firing a real request. See Testing a Map Remote and Testing a Map Local.