Thanks for the follow-up! I just checked again — for the failing request, the browser console only s
Thanks for the follow-up! I just checked again — for the failing request, the browser console only shows a "CORS error" with no actual status code returned. It seems the request was blocked at the browser level, likely due to missing CORS headers. So I can't see whether it's a 403 or something else from the server.
This behavior is inconsistent across routes, which all go through the same CORS middleware on our side. That’s why I’m wondering if Cloudflare Pages might be treating certain paths differently or applying stricter rules (maybe WAF or edge caching changes?).
This behavior is inconsistent across routes, which all go through the same CORS middleware on our side. That’s why I’m wondering if Cloudflare Pages might be treating certain paths differently or applying stricter rules (maybe WAF or edge caching changes?).


