Identify the R2 manifest validator to Cloudflare - #33
Merged
Merged
Conversation
Bot management on downloads.terraphim.ai answers the default Python-urllib User-Agent with 403, which has been failing the hourly r2-manifest-health workflow and local operator runs even though every channel object is healthy. Both fetch paths now send terraphim-r2-manifest-validator/1.0. Verified locally: all three binaries validate legacy=strict=1.21.16 with full size and SHA-256 checks. Refs #337
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.
Problem
The dispatched
r2-manifest-health.ymlrun 36193817261 failed withHTTP Error 403: Forbidden, and the same failure reproduces locally. Cause: bot management ondownloads.terraphim.aianswers the defaultPython-urllibUser-Agent with 403 (verified: same URL returns 200 for curl's UA, 403 forPython-urllib/3.10), so the hourly health workflow has been red independently of channel health.Change
scripts/validate-r2-manifests.pynow sendsUser-Agent: terraphim-r2-manifest-validator/1.0from both fetch paths (manifest load and streamed asset verification). Verified against the live channel after the v1.21.16 promotion: all three binaries validatelegacy=strict=1.21.16with full declared-size and SHA-256 enforcement. Thefile://-based contract tests are unaffected (18/18 pass).Refs #337