Repository navigation
chore: @profullstack/x402-gateway 0.15.3 (browsers are never 402'd) - #69
Merged
Merged
Conversation
…are never 402'd) Chrome 120-132 and Firefox 130 desktop user agents got the x402 JSON offer instead of the page; 0.15.3 lets any request that asks like a browser read it. Declared AI crawlers are still charged. profullstack/x402-gateway#28 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan15 finding(s) HIGH/CRITICAL: 1 | MEDIUM: 12 | LOW: 2
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Bumps @profullstack/x402-gateway to 0.15.3 (profullstack/x402-gateway#28): a desktop Chrome 120-132 or Firefox 130 user agent asking for a page got HTTP 402 x402 JSON instead of the page. 0.15.3 lets any request that asks like a browser (Accept text/html, page Sec-Fetch-Dest, Next.js RSC) read it; declared AI crawlers (GPTBot, ClaudeBot, CCBot) are still charged and search crawlers are untouched. Lockfile only otherwise.
🤖 Generated with Claude Code