Seems to work when you go to that link via the homepage but fails to load when you use a direct link or refresh the page. It appends a / to the URL when you use the direct link, which I assume is what breaks it.
Ah. Badly-implemented isomorphic rendering, with client-side routing that works, but a server-side implementation that’s partially broken.
I disable JavaScript in general for a significantly better experience of the web, and didn’t suspect anything like this since everything else was working perfectly.
Incidentally, I strongly oppose the use of client-side rendering for pages like this (not CSR in all cases, but yes for a site like this). Barring the small matter of this one broken page, the result is fairly uniformly inferior to the no-JavaScript version: it has a heavier footprint, doesn’t work as well (some history interactions are a touch dodgy, no loading throbber, can’t interrupt navigation with Escape, &c.), and feels slower than fresh page loads anyway. It’s foolish, harmful complexity.
I disable JavaScript in general for a significantly better experience of the web, and didn’t suspect anything like this since everything else was working perfectly.
Incidentally, I strongly oppose the use of client-side rendering for pages like this (not CSR in all cases, but yes for a site like this). Barring the small matter of this one broken page, the result is fairly uniformly inferior to the no-JavaScript version: it has a heavier footprint, doesn’t work as well (some history interactions are a touch dodgy, no loading throbber, can’t interrupt navigation with Escape, &c.), and feels slower than fresh page loads anyway. It’s foolish, harmful complexity.