Skip to content

docs: fix two 404 links in README - #3137

Open
rajanpanth wants to merge 2 commits into
hapijs:masterfrom
rajanpanth:docs/fix-dead-joi-dev-links
Open

docs: fix two 404 links in README#3137
rajanpanth wants to merge 2 commits into
hapijs:masterfrom
rajanpanth:docs/fix-dead-joi-dev-links

Conversation

@rajanpanth

Copy link
Copy Markdown

Two of the four "Useful resources" links in the README return 404:

Link Status Replacement
https://joi.dev/api/ 404 https://joi.dev/api/18.x.x
https://joi.dev/policies/ 404 https://joi.dev/policies/coc

joi.dev serves no index page at either /api/ or /policies/. The API reference lives under a version segment, and the policies section has no landing page — its first entry is the Code of Conduct, which is also where joi.dev's own homepage navigation points.

The other two resource links (/resources/status/#joi and /resources/changelog/) resolve fine and are untouched.

Separately, and outside the scope of this PR: joi.dev's own top navigation links to /api, which 404s for the same reason — worth fixing on the site side.

joi.dev has no index page at /api/ or /policies/. The API reference is
served at /api/18.x.x and the policies section starts at /policies/coc,
which is also where joi.dev's own navigation points.
@Marsup

Marsup commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

/api/ is redirecting, only the policies part is valid

joi.dev/api/ resolves client-side to /api/18.x.x in a browser, so it is
not broken. Only the /policies/ link is a genuine 404.
@rajanpanth

Copy link
Copy Markdown
Author

You're right, thanks. I checked with curl, which gets a hard 404 with no Location header, so I read it as broken. In a browser /api/ resolves client-side to /api/18.x.x and renders the API page, so nothing is actually wrong with that link.

/policies/ does not do the same. It stays put and renders the 404 page, in a browser as well as over curl.

Pushed a commit restoring the /api/ link. The PR is now just the one-line policies change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants