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

Messaging API

ServiceStack Documentation

ServiceStack Studio Preview - Announcements - ServiceStack Customer Forums

iis 7.5 - 401 response for CORS request in IIS with Windows Auth enabled - Stack Overflow

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

A Guide to Solving Those Mystifying CORS Issues

ServiceStack JsonServiceClient (TypeScript): Do not go to the requests after authentication from CORS - Stack Overflow

Got cors error on chrome in localhost env · Issue #39 · clerk/t3-turbo-and-clerk · GitHub

javascript - CORS issue on java web application - Stack Overflow

ServiceStack JsonServiceClient (TypeScript): Do not go to the requests after authentication from CORS - Stack Overflow

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

Ugo Lattanzi

Blazor WASM Bootstrap