Skip to main content
← Back to list
01Issue
BugOpenSwamp CLI
Assigneesstack72

Trailing slash on /extensions/@<namespace>/ returns 404

Opened by stack72 · 4/23/2026

Problem Statement

After #446 shipped the /extensions/@ namespace-browse route, adding a trailing slash to the URL (e.g. /extensions/@bixu/) returns a 404 instead of rendering the namespace listing. The non-slashed URL (/extensions/@bixu) works correctly.

Reproduction

  1. Visit https://swamp.club/extensions/@bixu — renders the namespace page.
  2. Visit https://swamp.club/extensions/@bixu/ — returns SIGNAL_LOST (404).

Expected Behavior

Trailing slashes should either be tolerated (serve the same page) or 301-redirect to the canonical non-slashed URL so there is only one indexable form per namespace.

Likely Cause

Fresh's file-system router matches /extensions/@[slug].tsx only for single-segment paths without a trailing slash. With the trailing slash, the request falls through to the /extensions/[...name].tsx catch-all, which sees "@bixu/" as the candidate extension name — that fails ExtensionName validation and renders NOT_FOUND.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED

Open

4/23/2026, 1:27:29 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack724/23/2026, 1:27:40 PM

Sign in to post a ripple.