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

ServiceStack v6

ServiceStack v6

Logging & Profiling UI

What Is a CORS Error and How to Fix It (3 Ways) - Bannerbear

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

How to Solve CORS Error in 2 min [WATCH THIS]

javascript - Problem with CORS policy when I use axios POST - Stack Overflow

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

ServiceStack v6

CORS errors and how to solve them

CORS failed to fetch error with custom HTTP connec - Power Platform Community

JsonServiceClient response filter problem ignores 400 & 401 responses - JavaScript - ServiceStack Customer Forums

Misleading CORS Errors – Dev Notes

Get rid of CORS error from client-end, by Aparna Chinnaiah, Nerd For Tech