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

Release History for Telerik Products

ServiceStack.AI

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

GitHub - NetCoreApps/TechStacks: TechStacks Web App created using Nuxt.js + Vuetify

ERROR : No Access-Control-Allow-Origin header is present · Issue #582 · jaredhanson/passport · GitHub

Messaging API

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

raulg ʻenehana – Hekili Tech

GitHub - ServiceStack/Studio: ServiceStack Studio

Messaging API

UpdateEventSubscriber responds 200 but doesn't update subscription · Issue #710 · ServiceStack/Issues · GitHub