fix: DSN token precedence — prefer Bearer, parse URL-shaped dsn (fixes #1) - #4
Merged
Conversation
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
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.
Fix: DSN token precedence — prefer Bearer, parse URL-shaped dsn
Fixes #1
Problem
When a client sends the full DSN URL (
http://TOKEN@host:3456/api/ingest/PROJECT_ID) in the JSON body'sdsnfield — which the official Claude Code hook does — the full URL shadowed the Bearer token. Prisma lookup fails searching for the full URL as a token.Result: all Claude Code events silently dropped with
401 Invalid DSN token.Fix (minimal — 6 lines added)
Files changed
apps/web/app/api/ingest/route.ts— DSN precedence fixCHANGELOG.md— v0.2.1 entry