Navigating back to root of custom domain page leads to a 404.

[nicksergeant]

I noticed this while writing up #178, but was hoping that it'd be fixed in the final merge of #181

If you navigate to https://demo.vercel.pub/ then click the link for "Announcing our $150M Series D" (https://demo.vercel.pub/150m-series-d), then use your browser's back button, you will get a 404.

Here's a GIF screencast of the bug:

[nicksergeant]

I was able to manually fix/patch this in my test repo like this in the middleware:

  // Next 13 sometimes appends 'index' to root paths after the page has loaded...
  let pathname = nextUrl.pathname;
  if (nextUrl.pathname === "/index") {
    pathname = "/";
  }

(but, I don't really understand the mechanism deeply enough to know whether this is a poor approach for a fix, or not)

[steven-tey]

Hey Nick! Thanks for reporting this! This is a bug in the Next.js /app directory – the team is aware of it and are actively fixing it now!

[nicksergeant]

@steven-tey awesome to hear! Let me know if I can help beta test any future potential fixes for this, also 👍

[steven-tey]

Closing this since we've migrated to the App Router as per #221 and this should be fixed now!