Map Remote
Map Remote sends a matching request somewhere other than where the app asked for it, and returns that server’s answer as if it came from the original one. The app under test is not changed and does not know.
Adding a rule
Section titled “Adding a rule”Select Map Remote in the sidebar and add a rule with:
| Field | What it does |
|---|---|
| Pattern | Which requests to redirect — the shared rule syntax (api.example.com, api.example.com/v1/*, /health) |
| Method | Any, or one HTTP method |
| Destination | Where to send it (see below) |
| Keep the original path | Append the original path after the destination’s own path. Off replaces the path outright |
| Keep the query string | Carry the original ?query over |
| Keep the original Host header | Keep sending the original Host: header instead of the destination’s |
The editor shows a live before → after preview for a sample URL as you type.
Destination formats
Section titled “Destination formats”| Destination | Result for https://api.example.com/v1/users?page=2 |
|---|---|
https://staging.example.com |
https://staging.example.com/v1/users?page=2 |
staging.example.com:8443/v2 |
https://staging.example.com:8443/v2/v1/users?page=2 (with Keep the original path on) |
/v2/users |
https://api.example.com/v2/users?page=2 — same host, new path |
http://10.0.0.5:3000 |
http://10.0.0.5:3000/v1/users?page=2 |
A destination without a scheme inherits the original request’s scheme.
Same server vs. a different server
Section titled “Same server vs. a different server”- Same origin (same scheme, host, and port) — HTTPGlass rewrites the request line on the connection that’s already open. Nothing else changes.
- Different origin — HTTPGlass opens its own connection to the destination, fetches the
response, and injects it into the original connection. This fetch does not follow
redirects, cache, or keep cookies; a
302from the destination is what the app sees.
The inspector shows where the request was sent, so a mapped request is never mistaken for a real call to the original host.
When to keep the Host header
Section titled “When to keep the Host header”Turn Keep the original Host header on when you’re pointing at one specific node or an IP address but the server still needs the real hostname for virtual-host routing or TLS SNI. Leave it off when the destination is a genuinely different service.
Order of operations
Section titled “Order of operations”When several rules match, the topmost one wins, so a narrow rule can sit above a broad one.
Same-origin Map Remote runs first, then Rewrite rules, then scripts, then a cross-origin detour, then breakpoints. A rewrite or script therefore sees the mapped path, not the original one.