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?

Dell Boomi Implementation Planning Guide, PDF, Json

Bypass Rate Limit Securing Future:Securing Cyberspace

google cloud platform - Stackdriver API metrics show many 429 errors, while quota is not exceeded - Stack Overflow

New feature: configurable web service rate limiting : Assertible

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

429 Error – Too Many Requests HTTP Code Explained

429 too many request? - PeerTube - Framacolibri

API Throttling with ServiceStack –

What Does HTTP Error 429: Too Many Requests Mean? How to Fix It

Cloud Computing Students Handbook - v1.3 - 115444, PDF, Cloud Computing

What Does HTTP Error 429: Too Many Requests Mean? How to Fix It

429 Too Many Requests errors - Azure