I'm experiencing the same issue I think. For me when hovering over the url it shows the internal route that middelware will send the user trough which is weird but it seems to be working when hosted on vercel. Locally I have none of these issues.

Same issue here

It's breaking all of our slugs 😬

+1

Tested on Vercel with Next 13.5.5, 13.5.6 and 14.0.1.

Same issue with a bit more trouble.

const Orders = async ({ params, searchParams }: OrdersProps) => {

  const orderId = params.orderId;
  const token = searchParams.token;

  const URL = `https:/my-domain.com/customer/v1/orders/${orderId}?token=${token}`;
  
  const res = await fetch(URL);

Example of call: http://my-web-app/orders/857258?token=ZGFIUmhmd1l4V3dSMk1Cc05jT2E5akprSlhWQ0puMmNlYWs3QldZcWp6ZEZQVGtTQjZhaFlLV2lzYTVnSmJQdnJhL0FZdGtJaVhNSG9yVUxyL2hXN3c9PQ==

On local: works fine.

On Vercel:

[GET] /orders/857258?token=ZGFIUmhmd1l4V3dSMk1Cc05jT2E5akprSlhWQ0puMmNlYWs3QldZcWp6ZEZQVGtTQjZhaFlLV2lzYTVnSmJQdnJhL0FZdGtJaVhNSG9yVUxyL2hXN3c9PQ%3D%3D&nxtPorderId=857258

== -> %3D%3D

And I am not sure to understand the &nxtPorderId=857258 here.

When I display orderId and token in the page, everything is fine, too.

I might try to see on Netlify.

Still having this issue on next 14.0.3. Has anyone managed to find a solution other than just changing your url params to not have a plus?

I've encountered same issue on Next.js 14.2.1

Also hitting this same bug, for me a workaround to replace the + doesn't really work since the urls have been indexed by search engines previously.

@ericledonge-betonprovincial - it's been a while, but did you end up trying this on Netlify? Might be an alternative for anyone who is really affected by this issue. Also, I imagine people not paying Vercel might help motivate someone to look into this issue.

As for me, luckily, I had control of the URL and I encountered this before anything went live so I was able to work around it.