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?

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

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

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

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

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

429 Error – Too Many Requests HTTP Code Explained

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

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

Rate-Limited request returns 429 but not the custom response body - Website, Application, Performance - Cloudflare Community

Rate Limiting at the CDN Edge ⋆ Mark McDonnell

429 Too Many Requests - KeyCDN Support

Enterprise Application Architecture With Net Core, PDF, Web Application

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