Fetch site.webmanifest with credentials - #9491
Merged
Merged
Conversation
A manifest is fetched without cookies by default, so Cloudflare challenges the request and it comes back 403 on every page. crossorigin="use-credentials" sends them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01549BYfDEpyce9GLgGnJqpm
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.
Every page logs this in the console:
It is not Rails.
MetaControllerskips authentication and just renders JSON, andthe 403 carries
cf-mitigated: challenge, so Cloudflare is answering before theapp sees the request. A manifest is fetched without credentials by default, so
Cloudflare sees a cookieless request and challenges it.
Adding
crossorigin="use-credentials"makes the browser send cookies with themanifest fetch, which is the conventional fix for exactly this.
This needs confirming in production, since the challenge only happens at the edge
and cannot be reproduced locally. If it does not clear it, the alternative is a
Cloudflare rule exempting
/site.webmanifest.Cosmetic either way: the manifest only supplies PWA install metadata, so nothing
user-facing is broken today. It is just noise in every console.
🤖 Generated with Claude Code
https://claude.ai/code/session_01549BYfDEpyce9GLgGnJqpm