Map Local
A Map Local rule answers a matching request itself. The server is never asked; the app gets the status, headers, and body you wrote. Use it to try a response the backend can’t produce yet, to reproduce an edge case on demand, or to keep working when the backend is down.
Adding a rule
Section titled “Adding a rule”Select Map Local in the sidebar, type a pattern (the shared rule syntax), and add it. Each rule has:
| Field | What it does |
|---|---|
| Method | Any, or one HTTP method |
| Status | The status code to answer with. 200 by default |
| Content-Type | Set on the response. application/json by default |
| Body | The response body |
| Headers | Extra response headers — Set-Cookie, CORS headers, and so on |
| Enabled | Switch a rule off without deleting it |
Content-Length is filled in for you. When several rules match, the first enabled one in the
list answers.
In the traffic table
Section titled “In the traffic table”A request answered by Map Local still appears as a row, and the inspector says it was answered locally and the server was never asked — so a mapped response is never mistaken for a real one.
Map Local or something else?
Section titled “Map Local or something else?”- To send the request to a different server and return its real answer, use Map Remote.
- To change part of a real response — one header, one field — use Rewrite or a script.
- To edit a response once, by hand, use a breakpoint.