Fix Turnstile CORS preflight breaking session mint - #465
Merged
Merged
Conversation
Send turnstileToken as a GET query param instead of X-Turnstile-Token. API Gateway OPTIONS does not allow the custom header, so browsers blocked session mint with Failed to fetch (Unable to connect error in the UI). Co-authored-by: xenodus <xenodus@gmail.com>
Wait for Turnstile/session bootstrap before auto-searching ?s= URLs (trending links). Do not mark landing search handled until bootstrap completes; retry when maintenance mode clears. Co-authored-by: xenodus <xenodus@gmail.com>
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
2 participants
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.
Root cause
X-Turnstile-Tokentriggered a browser preflight that API Gateway does not allow → session mint failed (Failed to fetch→ "Unable to connect").?s=URLs (trending links) only runs aftersessionBootstrapped. With Turnstile + failed session mint, search never started. Init effect also sethasInitializedRefbefore checking maintenance mode, which could skip the landing search permanently.Fix
?turnstileToken=query param (no custom-header preflight).Deploy
Merge and deploy Lambda + frontend. No API Gateway change.
Testing
make test?s=→ search runs automatically