Fix Safari ITP submission failure on /new_submission#67
Draft
eduardosanchezg wants to merge 1 commit into
Draft
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
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.
On Safari, the HF Space proxy requires the
__signJWT token to authenticate requests. Safari's Intelligent Tracking Prevention (ITP) blocks the session cookie that Chrome uses, so POST requests to/new_submissionare rejected by the proxy before reachinguvicorn, returning an HTML 401 instead of JSON.response.json()then throwsSyntaxError: The string did not match the expected pattern(Safari's wording for a JSON parse failure).Fix: Extract
__signfrom the current page URL and forward it on the POST, plus add credentials: 'include' to ensure cookies are sent where available.