[9.5.4-canary.18] Different router.asPath between server and client.

[nghiepdev]

Bug report

From 9.5.4-canary.18 router.asPath in the sever-side return incorrect value.

Describe the bug

// next.config.js
module.exports = {
  rewrites() {
    return [
      {
        source: "/my-post",
        destination: "/post"
      }
    ];
  }
};

To Reproduce

https://codesandbox.io/s/sharp-cannon-kcsio?file=/pages/post.js
Directly access /my-post url

Expected behavior

The router.asPath always return /my-post.

Additional context

#17082

[ijjk]

Hi, this should be fixed in v9.5.4-canary.20 of Next.js, please upgrade and give it a try!

[nghiepdev]

@ijjk v9.5.4-canary.20 The problem still has not resolved 😿
https://codesandbox.io/s/sharp-cannon-kcsio?file=/pages/post.js

[ijjk]

@nghiepit which part isn't resolved on that codesandbox link? It looks like the asPath is the expected value when visiting /my-post. We have also added these cases to our test suite which are passing.

[nghiepdev]

In my local project and export codesanbox.example.zip both are the same problem.

[ijjk]

@nghiepit I took another look at your reproduction and your issue doesn't appear to be related to the GS(S)P asPath resolving like I thought so I opened a new issue to track the actual problem you are encountering here. Thanks for reporting back that the issue wasn't resolved!

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.