Redirect to other Netlify apps using subdirectories

[nathanmartin]

@kndshein

The JS seems to be blocked by CORS. Would you happen to have a tip on how I should continue here?

I believe you could solve this with 3.2.1 in this guide:

[Support Guide] Handling CORS on Netlify

Last reviewed by Netlify Support in July 2025 CORS stands for Cross Origin Resource Sharing. It is a HTTP header that tells the browsers how to handle a request from a certain origin to for an asset on your website. You can read more about it on Cross-Origin Resource Sharing (CORS) - HTTP | MDN (mozilla.org). By definition, an origin consists of scheme, domain and port. For example: https://www.example.com/ https:// is the scheme www.example.com is the domain 443 is the port (HTTPS is serve…

---

@kndshein

This seems more straightforward in some respect, however, I’m not sure where to start. Additionally, my intuition tells me that I’m bound to run into CORS here as well.

It would be very straightforward if each site was requesting its assets from an easily identified sub-folder, something like:

/assets-v1/* https://amseeyou-v1.netlify.app/assets-v1/:splat 200!
/assets-v2/* https://amseeyou-v2.netlify.app/assets-v2/:splat 200!
/assets-v3/* https://amseeyou-v3.netlify.app/assets-v3/:splat 200!

But they currently aren’t, they’re more generic (/assets/, /static/assets/ etc) so they can’t be blanket rewritten with a wildcard, and they also consist of generative sha’s so manually specifying each individual asset would break when your code changes.

Forgot to mention, you wouldn’t run in to CORS with this, in the same way that people use it proxy an external API to avoid CORS (as per https://docs.netlify.com/routing/redirects/rewrites-proxies/#proxy-to-another-service).