Next.js: Possible bug: 308 redirects for assets when using trailing slashes option

Created on 30 Jun 2020  路  3Comments  路  Source: vercel/next.js

Bug report

We are using a pre-release version to make use of #13333 for trailing slashes. The routes work fine with trailing slashes but we noticed that the server now redirects asset requests to include trailing slashes, too. We are not sure if we are doing something wrong or if this is a bug. In case it is a bug, we wanted to bring this to your attention so that it can be fixed before the 9.4.5 release.

Expected behavior

The server does not redirect the requests, i.e. responds with status code 200 instead of 308.

Screenshots

Screenshot 2020-06-30 at 21 39 13

System information

  • Version of Next.js: 9.4.5-canary.20
  • Version of Node.js: 14.0.5

Additional context

@Janpot for visibility.

bug p0

Most helpful comment

Thank you, can confirm that it was fixed in a later version and works now for us. :-)

All 3 comments

@ianflorian there have been some fixes (https://github.com/vercel/next.js/pull/14681) in the latest canary. Can you try to upgrade to 9.4.5-canary.25?

Yep this was already fixed by @Janpot 馃憤

Thank you, can confirm that it was fixed in a later version and works now for us. :-)

Was this page helpful?
0 / 5 - 0 ratings