fix(cloud): forward /api/sentry-tunnel to Sentry ingest#277
Merged
RhysSullivan merged 1 commit intomainfrom Apr 17, 2026
Merged
fix(cloud): forward /api/sentry-tunnel to Sentry ingest#277RhysSullivan merged 1 commit intomainfrom
RhysSullivan merged 1 commit intomainfrom
Conversation
routes/__root.tsx configures the browser Sentry SDK with tunnel: '/api/sentry-tunnel' but nothing served that path — every error report came back RouteNotFound. Add a request middleware (before the /api/* router) that intercepts POST /api/sentry-tunnel, parses the envelope's first-line header to recover the DSN, and forwards the raw body to https://<dsn host>/api/<project>/envelope/. The envelope's DSN is validated against env.SENTRY_DSN (host + pathname) to keep this from being an open relay for the Sentry ingest. Missing DSN → 204; bad envelope → 400.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
routes/__root.tsx configures the browser Sentry SDK with
tunnel: '/api/sentry-tunnel' but nothing served that path — every
error report came back RouteNotFound.
Add a request middleware (before the /api/* router) that intercepts
POST /api/sentry-tunnel, parses the envelope's first-line header to
recover the DSN, and forwards the raw body to
https:///api//envelope/. The envelope's DSN is
validated against env.SENTRY_DSN (host + pathname) to keep this from
being an open relay for the Sentry ingest. Missing DSN → 204; bad
envelope → 400.