Magued ABOU ALI

Maybe that is what you looking for ? `let client = new WebSocketClient({tlsOptions: {rejectUnauthorized: false}});`

I can confirm. I am seeing similar issues when trying to prefetch dynamic routes like `app/test/[testId]/leaf/page.tsx` where the prefetching systematically fails **on Vercel** (but works fine with next dev &...

So the behavior you described is due to forcing `OptimisticNavigation` when calling the router in `link.tsx` when prefetching is disabled. Not sure it was the intended behavior, but seems like...

You'll find the repo to reproduce [here](https://github.com/Smirow/test-headers-vercel). Tested on Next 13.0.1.

Strangely enough, when trying with `testId=[testId]`, Vercel matches the corrected route (`x-matched-path: /test/[testId]/leaf.rsc`) and it works as expected (with `testId=[testId]` which is not really useful). Definitely something going on with...

To help the investigation, rewriting the url in `middleware.ts` with the **same url** seems to fix the issue on Vercel: ```javascript return NextResponse.rewrite(new URL(request.nextUrl.pathname, request.url)); ```

@timneutkens thanks for the transfer, but to be clear and as mentioned, as far as my testing goes, this behavior is only replicable on Vercel.

Thanks @ijjk ! Working as expected.

Coming from #8458. I really like the `group` idea to handle the splitting behaviour, it can be a nice way to prevent some cold starts for `node` runtime and really...

I also find the current kit and Svelte documentation pretty good (and I recently learned Svelte and kit on those). The tutorial is brillant. I think I never grasped the...