Server Action Redirect Fails on Absolute URLs from the Same Host

[giulianovarriale]

Summary

We have multiple apps running under the same host and need to redirect users to different applications on specific actions. However, Next.js assumes all redirects within the same host belong to the same application, leading it to resolve and stream the route itself. This behavior results in a "Not Found" page when the target route belongs to a different application.
I found a related issue: #64413 and its corresponding fix: #64604. However, I don’t understand how this fix could help without the need to set a base path and configure some rewrites which is not optimal for my use case.

Questions:

• Are there alternative solutions to address this issue?
• Wouldn’t it be beneficial to allow the developers to control this behaviour by introducing a parameter that tells nextjs that the targeted url is an external app so that it skips the resolving and streaming part?

Additional information

No response

Example

No response

[icyJoseph]

I guess, a route handler would fix this? You could just send a 301/302/307/307, etc, to the client, but this would have to be done the old way, <form action="/path-to-the-route-handler" method="POST"> kind of thing...

If you set the basePath though, the sub-domain where your Next.js app lives, then links, and other stuff should work fine, like, relative to that basePath, what problem do you see, that'd need rewrites? In all likely hood I am missing some details here.

[giulianovarriale]

The route handler is an option we are considering indeed.

About the base path approach, you might be right, perhaps a rewrite is not needed. I have to try it out, but even so, our routes are pretty dynamic and the apps are not split by a subdomain or any kind of path acting as a namespace.