#Inconsistent Redirect Behaviour in Middleware

2 messages · Page 1 of 1 (latest)

misty pond
#

I'm confused with inconsistent NextResponse.redirect() behaviour in Dev vs Prod and not sure who to ask or where it's happening.
My team believe we need to upgrade next, but I'm concerned that might not work.

In Dev:
Redirecting from / to /route/pathname/, I get status codes 307 -> 200 ✅
Redirecting from /route/pathname/ to /route/pathname-two/, I get status codes 307 -> 200 ✅

In Prod:
My trailing slash is removed from redirectUrl /route/pathname/ and re-added causing a 308 in the chain.

Redirecting from / to /route/pathname/, I get status codes 307 -> 308 -> 200 ❌
Redirecting from /route/pathname/ to /route/pathname-two/, I get status codes 307 -> 200 ✅

next.config.js

  • trailingSlash: true

Anyone have any top of mind ideas?

Thank you

lean parrotBOT
#

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)