next.config.js => Fallback and filetypes
Unanswered
Maine Coon posted this in #help-forum
Maine CoonOP
Hi All,
I am working to do a "fallback" configuration via the next.config and I am running into a major issue that I can't seem to solve. Hopefully it's already been solved and just not documented in a way I can search.
Next.js 13.5.2
When requesting a resource, if I include the full filepath & extention, it is rendered as expected:
However when I request that same resource without the
I have hundreds of templates in the legacy app that I need to fall back to, and in those, I'm leveraging tons of url paremeters, as well as getting visits to direct URLS. What can I do to have it properly fallback, without redirecting?
I am working to do a "fallback" configuration via the next.config and I am running into a major issue that I can't seem to solve. Hopefully it's already been solved and just not documented in a way I can search.
Next.js 13.5.2
When requesting a resource, if I include the full filepath & extention, it is rendered as expected:
https://<ExampleVercelApp>/FallbackUrl/index.phpHowever when I request that same resource without the
index.php I get a redirect to the legacy app URL instead of "Falling back" as it would with filetype appended as expected.I have hundreds of templates in the legacy app that I need to fall back to, and in those, I'm leveraging tons of url paremeters, as well as getting visits to direct URLS. What can I do to have it properly fallback, without redirecting?
2 Replies
Maine CoonOP
I'm digging through build code right now to see if there is a undocumented arguments I could leverage, but unable to find anything.
Maine CoonOP
This question is still unanswered, might prevent a Vercel deployment outright if we're forced to deploy a router in front of the two apps.