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?

Auth0 login rate - Auth0 Community

How to Fix the HTTP 429 Too Many Requests Error

429 Error – Too Many Requests HTTP Code Explained

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

ServiceStack CORS Issue with React - API Design - ServiceStack Customer Forums

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

429 Too Many Requests - API Error Code [Solution]

429 Error – Too Many Requests HTTP Code Explained

Troubleshooting HTTP 429 errors in Oracle Integration

CS544_Project/tag_count.txt at master · weichenzhao/CS544_Project · GitHub

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

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