Repository navigation
fix(nuxt): Answer managed tunnel requests on Cloudflare - #26365
Conversation
size-limit report 📦Compared: 4f0d802 (PR test merge using develop at 8c8f0d4) Against: 8c8f0d4 (develop) · base run #66474 ✅ Baseline matches: this diff contains only this PR's changes.
|
Optional E2E testsAll optional checks were successful. 8 successful. See the run. Successful checks
|
7f46250 to
0a0de1a
Compare
`sentryCloudflareNitroPlugin` matched the tunnel before `wrapRequestHandler` created the client. No client was current, so the match always failed, the tunnel request got no body, and the app answered it instead of the SDK. The plugin now matches the tunnel inside the `wrapRequestHandler` callback, where the client exists, and passes the body Nitro read only to the tunnel handler. Other requests still get no body, so their bodies stay off their events. The `nuxt-4-cloudflare` tunnel e2e test only checked for a 200, which the app returns too. It now waits for the forwarded envelope, and it fails without this fix. Closes #26364 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0a0de1a to
535d3e1
Compare
|
@s1gr1d The tunnel coverage now lives in its own test. Your review was on 7f46250, which made the The branch already sits on |
sentryCloudflareNitroPluginmatched the tunnel beforewrapRequestHandlercreated the client. No client was current, so the match always failed, the tunnel request got no body, and the app answered it instead of the SDK.The plugin now matches the tunnel inside the
wrapRequestHandlercallback, where the client exists, and passes the body Nitro read only to the tunnel handler. Other requests still get no body, so their bodies stay off their events.The
nuxt-4-cloudflaretunnel e2e test only checked for a 200, which the app returns too. It now waits for the forwarded envelope, and it fails without this fix.Closes #26364