CORS and other errors appearing with caching module enabled...
We are currently using A10 Thunder for load balancing, but we also have the caching module enabled for our in-house web applications.
Fairly recently, we began creating Angular (8) applications that call .NET CORE 3.x APIs. We develop these locally and things work fine, but when we ported them to our development environment that uses IIS and Windows servers through the A10 thunder, the API calls returned CORS errors. We could not replicate these locally, so our admin disabled the caching module on our A10 and everything began to work again.
We also noticed that Angular apps built with development configuration (i.e., non-optimized) run fine with the A10 Cache enabled, but optimized Angular apps (built with "ng build --prod") did not. With caching turned off, the optimized apps also began working.
We're not really sure where to begin troubleshooting this issue. Is the A10 looking for additional headers with caching? Is there some configuration we need on the A10 to address this issue? Any guidance or direction would be appreciated!