Follow a request through the proxy
Distinguish a tunnel, a response served locally, and a response forwarded from the origin.
A single refresh can produce a catalog request, several artwork requests and background traffic from other apps. Before you decide that the backend sent the wrong response, establish three things: which request belongs to the action, whether its contents were visible, and who supplied the response.
Find the connection your app actually used
Trigger one refresh and note the time. In Table or Explorer, narrow the capture to the expected host. If the app sent plain HTTP, you can inspect the request directly. For HTTPS, the client may first ask the proxy to open a connection with CONNECT. Seeing that host is evidence of routing; it isn’t evidence of a particular HTTP path or response.
Check whether the session was tunneled or inspected
With a tunnel, JoesProxy passes encrypted traffic through. You can investigate the connection without reading the JSON inside it. With inspection enabled for a permitted host, the client must accept the certificate presented by JoesProxy before an HTTP exchange can be inspected. A failed handshake is not a successful tunnel. If an inspected session has no stored body, check retention and omission separately from trust.
Identify the response source
A matching Map Local rule can serve a test file without fetching the original. Map Remote can forward the request to another backend. A Block rule can return a synthetic failure. Select the new session and inspect its source before treating an error as a server incident. A rule that exists in the workspace is not necessarily the rule that matched this request.
Compare two runs
Take a catalog request from your own test app. Record its normal response, then map that endpoint to a local fixture with one conspicuously different title. Refresh once. Check the selected request’s attribution and returned title; then look at the app. If the new title reached the client but the old title remains on screen, investigate what the app did after delivery. Disable the rule and repeat to establish the baseline again.