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?

ServiceStack CORS setup fails due to response to pre-flight doesn't pass access control check - Stack Overflow

429 Error – Too Many Requests HTTP Code Explained

Implement API rate limiting to reduce attack surfaces

Diagnose failures and exceptions with Azure Application Insights - Azure Monitor

New feature: configurable web service rate limiting : Assertible

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

Cors issue when returning error in filter - ServiceStack Customer Forums

How to Fix the HTTP 429 Too Many Requests Error

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

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

Information: API Rate Limit - RightSignature API - Discussions

429 too many requests - installation - Discourse Meta