Repository navigation
links: check github.com blob links through the raw host - #31
Merged
Merged
Conversation
github.com answers curl's requests for blob pages with 503 most of the time (7 of 8 locally on 2026-10-10; it turned go-ndarray/docs main red, all 3 attempts on 3 runs). The raw host answers 200 for an existing file and 404 for a missing one, which is what a blob link claims, so the check asks raw.githubusercontent.com/<o>/<r>/<ref>/<path>. Port of go-ndarray/docs#30; this site's two blob links pass today by luck. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
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.
Port of go-ndarray/docs#30.
On 2026-10-10, github.com answered curl's requests for
blob/pages with 503 most of the time: 7 of 8 locally, and all 3 attempts on 3 consecutive runs of go-ndarray/docsmain. A browser User-Agent got 200, and githubstatus.com reported no incident. This site has two blob links, both pinned tov0.28.0. They passed on the last run ofmain, but only by luck.A blob link claims that a file exists at a ref, so the check now asks
raw.githubusercontent.com/<owner>/<repo>/<ref>/<path>, with the anchor and query removed. That host returns 200 for an existing file and 404 for a missing one, so a broken link is still caught. Before pushing, I confirmed that both links resolve this way (200, 200).🤖 Generated with Claude Code