redirect on edge should clear query params

[roelandxyz]

I have a middleware function that does a NextResponse.redirect("/dashboard")
This works fine, but when I deploy to Vercel, the query params are not removed.

Example

this: https://authedge.vercel.app/?foo=bar
redirects to: https://authedge.vercel.app/dashboard?foo=bar
(after login, I can create a simpler example without auth if needed)

this: http://localhost:3000/?foo=bar
redirects to: http://localhost:3000/dashboard

Here is the source:
https://github.com/roelandmoors/NextJsGoogleAuthOnEdge

The problem I have now is that after an oauth2 callback I do a redirect. That should clear the query params, but now I get something like this:
https://authedge.vercel.app/dashboard?scope=profile%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&state=nothingyet&code=4%2F0...

[roelandxyz]

I got the same problem with a normal redirect (not using NextResponse):

 return new Response(null, {
      status: 302,
      headers: {
        location: "https://authedge.vercel.app/dashboard",
      },
 });

Not sure how it should work now, but local dev behaves different than when deployed.

Maybe create an issue?

[roelandxyz]

Looks like the query params get merged:

  if (req.nextUrl.pathname.startsWith("/testnormal")) {
    return new Response(null, {
      status: 302,
      headers: {
        location: "https://authedge.vercel.app/dashboard?test=1234",
      },
    });
  }

this: https://authedge.vercel.app/testnormal?foo=bar
redirects to: https://authedge.vercel.app/dashboard?foo=bar&test=1234

But you can override the query params. So now I solve it like this:

NextResponse.redirect("/dashboard?scope=&state=&code=");

[roelandxyz]

Solution: override the query params:

NextResponse.redirect("/dashboard?scope=&state=&code=");