Disable SPA fallback for some paths/file extensions

Hi all, we recently had a problematic cloudflare pages deploy where users in some of regions weren’t able to access one of our latest css files.

The site is react, so per the behavior described here, assets that are actual files are served first, but if they aren’t found then it routes back to the root index.html.

During this deploy, it seems that some regional users that had refreshed close to the deploy weren’t able to fetch the latest /static/css/main.551913c.css file, which resulted in pages responding with the content of index.html, at which point the users browsers cached that as a valid response.

Is there anyway in Cloudflare Pages to prevent the spa fallback for certain paths or certain extensions to ensure this doesn’t happen again?

You should be able to create a 404.html in those paths