Repository navigation
Conversation
logaretm
added this pull request to stack #25201
October 8, 2026 15:45
…om the DSN Browser and server SDKs can now derive the same opaque tunnel path from the DSN with `getTunnelPath`, so they agree on it without a build step. `isTunnelRequest` and `handleTunnelRequestIfMatched` let a server wrapper serve the tunnel when its client has `_managedTunnel` set, which `resolveServerTunnelOption` derives from the `tunnel` option. `allowedDsns` defaults to the client's DSN and the forward to Sentry runs with tracing suppressed.
logaretm
force-pushed
the
awad/tunnel-core-dsn-path
branch
from
October 8, 2026 16:05
af27973 to
a2af1e1
Compare
logaretm
changed the title
This branch has not been deployed
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.
Each framework tunnel picked its own path at build time and needed a build step to share it with the client. This added complexity around how to pass that around, which is most determined by the framework, platform and runtime.
I'm pursuing an idea here to use a deterministic URL based on the DSN which would be present in both client/server setups where each can derive it separately, from within the runtime rather than the build-time.
It seems possible in all SSR frameworks except Next.js so I will see how far this goes.