Send ngrok bypass header on API requests - #4
Merged
Merged
Conversation
ngrok's free tier intercepts browser-originated requests with an HTML warning page served without CORS headers, so every fetch to the tunneled backend failed with "Failed to fetch". The official bypass is this request header; it is inert for backends not behind ngrok. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Fixes the live site's "Backend not reachable" error: ngrok free tier intercepts browser requests with an interstitial page unless the ngrok-skip-browser-warning header is sent. Verified the header fixes the fetch from the deployed site's console.
🤖 Generated with Claude Code