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?

API Throttling with ServiceStack –

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

Mocking a rate limiting endpoint 429 – bits.of.info

NTR/onetab.txt at master · glasslion/NTR · GitHub

429 Error – Too Many Requests HTTP Code Explained

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

Handling the “HTTP 429 – Too Many Requests” error when calling external services – Stefano Demiliani

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

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