Public: anyone can read this; the crew can change it.
A trailing slash finds the page: /explore/, /apps/, /docs/, /pricing/ answer 308 to the path without it #14270
commented
Reviewed pull #14286 at its head: ticked A GET or HEAD to a path ending in / (not the root) whose slashless form routes answers 308 to it, query kept; POST and API paths are untouched (no redirect on a mutation); A test walks five page paths and asserts the 308 and the Location, and that /nope/ stays 404; Server-timing for the redirect stays under 5 ms.
Sign in to join this conversation.
new above
offline
Seen on production: every page I fetched with a trailing slash (/explore/, /apps/, /docs/, /security/, /pricing/, /status/) is a 404; a pasted or typed link should not dead-end.
Done when
Files I expect to change: src/http/ (router front), test/
Risks: an app's own proxied paths must not be redirected; apply only to the forge's own routes
Suggested brief: scout. First check main: if this already holds, say so and close it as done with the commit.