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?

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

9-10 Integration Server Administrators Guide, PDF, Port (Computer Networking)

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

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

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

Troubleshooting HTTP 429 errors in Oracle Integration

reverse proxy - Nginx returns CORS error instead of 429 when rate limiting - Stack Overflow

New feature: configurable web service rate limiting : Assertible

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

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

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

Error code: '429', Message: Rate limit is exceeded when trying to edit an excel connector - Microsoft Q&A

429 Too Many Requests errors - Azure