Rate Limit (429) and CORS - ServiceStack - ServiceStack Customer Forums

I have implemented my own Rate Limit in SS. However, as the service itself is called from a SPA with CORS enabled, the actual Http Error 429 is not passed through to the SPA, instead I get the CORS error Access to fetch at 'https://(webapi)/json/reply/XXXX' from origin '(website)' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'. Is there a way to avoid this?

Rate-Limited request returns 429 but not the custom response body - Website, Application, Performance - Cloudflare Community

How to Fix the HTTP 429 Too Many Requests Error

jchannon.github.io/feed.xml at master · jchannon/jchannon.github.io · GitHub

jchannon.github.io/feed.xml at master · jchannon/jchannon.github.io · GitHub

jchannon.github.io/feed.xml at master · jchannon/jchannon.github.io · GitHub

router/CHANGELOG.md at dev · apollographql/router · GitHub

Rest Connector 429 Error - Too Many requests - Qlik Community - 134924

Laravel error 429 (Too Many Requests) : How to check and log requests count? - Stack Overflow

Limit in route Services per class? - Routing - ServiceStack Customer Forums

How to Fix 429 Too Many Requests Error Code: 6 Methods

Graph API - Increase Rate Limiting/ Throttling - Microsoft Q&A