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?

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

429 Error – Too Many Requests HTTP Code Explained

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

How to Fix the HTTP 429 Too Many Requests Error

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

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

Cors issue when returning error in filter - ServiceStack Customer Forums

Elastic agents reporting error: status code: 429, fleet-server returned an error: MaxLimit - Elasticsearch - Discuss the Elastic Stack

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

Error: failed to perform any bulk index operations: 429 Too Many Requests - Elastic Agent - Discuss the Elastic Stack

Bypass Rate Limit Securing Future:Securing Cyberspace

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

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

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

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