Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "gpoluccimv"

I am a long time customer of ASP.NET ZERO and have used this product at several companies. I think i've bought 3 licenses so far, and i'm on my fourth soon. I just recently switched to Angular 2 and Asp.net Core. Perhaps it wasn't the best decision. My project is using v5.5.2 of Asp.Net Zero's Angular 2 with ASP.NET Core template.

I am trying to deploy my application to IIS. The aspnet_core application that hosts swagger and the service comes up and runs fine. It is running on https://subdomain.domain.com:8080.

On the same server I have the Angular_UI running on https://subdomain.domain.com as the Default Web Site. My understanding is that these are two different origins and CORS information should be passed between them.

In appsettings.production.json I have the follwing:

"App": { "WebSiteRootAddress": "https://subdomain.domain.com/", "ServerRootAddress": "https://subdomain.domain.com:8080/", "ClientRootAddress": "https://subdomain.domain.com/", "CorsOrigins": "https://subdomain.domain.com,http://subdomain.domain.com/,http://localhost:49152", },

Again, the Swagger UI comes up just fine and i am able to successfully execute CheckDatabase; i am also able to use the Authorize button to login successfully.

When the Angular application starts up it shows a gray page and the loading spinner. It then times out on the request below with the following error:

Failed to load https://subdomain.domain.com:8080/AbpUserConfiguration/GetAll: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://subdomain.domain.com' is therefore not allowed access.

I have searched this forum and the wider web to figure this out without luck. Can anybody help me? It's urgent, as i am demooing this for the CEO during his board meeting early this week.

Many thanks!

Showing 1 to 1 of 1 entries