Cors issue when returning error in filter - ServiceStack Customer

When we are having some back to back API calls, on the Web Client side we are hitting CORS issues. We found that the Request Headers are set correctly but still CORS are hit. We found that internally the APIs error out with Error Code 429 – Too many requests. See image attached. This response header should be set correctly to inform Web Client that the error is 429 and not CORS. The filter we have is a throttling filter and the Cors issue happens when it return the 429 error public Thro

logging - What to See Trace Logs for Azure App Service? - Stack Overflow

Bypassing CORS Error with Webpack Dev Server, by DJ

Authentication Chain Principles

GitHub - ServiceStack/Studio: ServiceStack Studio

Release History for Telerik Products

API Error: Failed to fetch. Does the server allow CORS?status: undefined - AppGyver

php - How do i fix this Cors issue. I'm really stuck - Stack Overflow

Cors issue when returning error in filter - ServiceStack Customer Forums

Python Add ServiceStack Reference

CORS Error in React

Chrome javascript error: Refused to get unsafe header X-Response-Time with servicestack - Stack Overflow