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?

429 Too Many Requests errors - Azure

Tag-Suggestion-stackoverflow/unique_tags_count.csv at master · Shruti-96/Tag-Suggestion-stackoverflow · GitHub

Diagnose failures and exceptions with Azure Application Insights - Azure Monitor

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

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

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

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

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

Error: 429 Too Many Requests — You've been rate limited, by Bearer

Modern Web Development With ASP - NET Core 3, 2nd Edition, Ricardo Peres, 2020 Packt Publishing, PDF, Tag (Metadata)