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?

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

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

HTTP Status Code 429: What Is the 429 Too Many Requests Error?

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

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

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

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

429 Error – Too Many Requests HTTP Code Explained

Cors issue when returning error in filter - ServiceStack Customer Forums

Enterprise Application Architecture With Net Core, PDF, Web Application

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

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

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

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