Repository navigation
Retire GitHub Pages: http-arena.com is the site's address, readable from any origin as before - #1565
Merged
Merged
Conversation
…rom any origin as before The domain now points at the genhttp.dev lambda, where www.http-arena.com redirects to http-arena.com, so: - deploy.yml goes. It deployed to a Pages site nothing points at any more (its custom domain is unset and https://mda2av.github.io/HttpArena/ answers 404); the site is published by publish-genhttp.yml, by hand. - The site's address is https://http-arena.com: SITE in gen_leaderboard_data.py (canonical links, og:url, the sitemap, llms.txt, the cards' footers), the board's canonical link, robots.txt, the README and docs, the OpenAPI specs and validate.sh's doc links. Before, every one of them pointed at a 301. Entries' own files that link the site are left to them; the redirect keeps them working, and shields.io follows it for the badges. - The lambda's site answers with Access-Control-Allow-Origin: *, as Pages did: the docs' "Browse" links open openapi.json in Redoc, which reads it from its own origin and could not since the move. The smoke test checks it.
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.
The domain now points at the genhttp.dev lambda, and
www.http-arena.comredirects tohttp-arena.com. This PR is the follow-up to #1563, which fixes the publish run.deploy.ymlis removed. It deployed to a Pages site that nothing points at anymore: Pages has no custom domain set, andhttps://mda2av.github.io/HttpArena/answers 404. The site is published only bypublish-genhttp.yml, run by hand. That workflow also runs the badge parity check, so the check isn't lost.https://http-arena.com. This changesSITEingen_leaderboard_data.py(canonical links, og:url, the sitemap, llms.txt, the social-card footers), the board's canonical link,robots.txt, the README, the docs, the OpenAPI specs andvalidate.sh's doc links. Each of these pointed at a 301 before. Files insideframeworks/that link to the site are left to their maintainers, since the redirect keeps them working. shields.io follows it too, so existing README badges still render.Access-Control-Allow-Origin: *, as Pages did. The docs' "Browse" links openopenapi.jsonin Redoc, which reads it from another origin and has been blocked since the move. Only the site gets the header, notapi/. The smoke test now checks for it.Since
site/lambda/changes, the next publish saves a version. If #1563 merges first, that one version carries both PRs' changes.The committed
site/leaderboard/data.jsandsearch.jsare left alone. They were already out of date on main, and the publish workflow regenerates them anyway.Checked:
--no-logs, produces 1,801 files with nowww.http-arena.comin them. Canonical links, sitemap<loc>, og:url androbots.txtall usehttps://http-arena.com.check_badge_parity.jspasses: 1,026 ranks match.site/lambda/, followingtests/README.md, and published this site to it. Site responses carry the header on 200, 301 and 404, whileapi/sitedoes not.smoke.mjspasses all 12 checks, including the new one.🤖 Generated with Claude Code