Request Mirroring

Status: Implemented

Overview

Request mirroring duplicates incoming tunnel traffic to a secondary upstream so that developers can observe production-like requests against a development or staging environment without affecting the primary response path.

Design

• The edge server clones each inbound HTTP request and forwards the copy to a configurable mirror target after delivering the original response.
• Mirror responses are discarded (fire-and-forget) to avoid adding latency to the primary request path.
• Mirroring is opt-in per tunnel via the dashboard or API.

Considerations

• Idempotency: mirrored POST/PUT/DELETE requests will execute side-effects on the mirror target. Users should ensure the mirror environment can tolerate duplicate writes.
• Load: mirroring doubles outbound traffic from the edge. Rate limits apply independently to the mirror target.