CORS Errors with sub-directories when developing and testing with LocalHost (MS MVC Razor)

[jjborland]

I am receiving numerous errors about loading WebAwesome components, as soon as I go down a level in an _Layout.vbhtml file.

The attachment shows several errors, but this is the first one - which points to the solid issue:

from origin 'https://localhost:44333' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
menu.js:1 Failed to load resource: net::ERR_FAILED

Anyone have workarounds? I could certainly create a whole setup where it works from a local build during localhost testing, but then I'd have to rebuild everyt ime a new version comes out :(

ErrorMessagesInDeveloperTools.txt

[claviska]

It looks like the CDN isn't serving those files. It's setup to allow all requests from localhost, though, so this is strange. Does your dev setup have a proxy that might be doing something with the requests before they go out? Unfortunately, this doesn't give us a lot to go on so I'm just guessing.

[jjborland]

Ok, here is a deeper dive into the directory structure -

This is an MS MVC project inside a solution.

Inside the project in the Views\Shared folder is _Layout.vbhtml which calls the WebAwesome CDN -

<!-- WebAwesome Loader -->
<script src="https://kit.webawesome.com/<MYKITcode>.js" crossorigin="anonymous"></script>

There are no other CDN or scripts above this line.

On every load of the CDN, the page comes back with the CORS errors. The _Layout.vbhtml is loded correctly and the elements on it work correctly, but as I put more components in, I am not getting the responses back that I should - not loading lists and so on.

[claviska]

This is an MS MVC project inside a solution.

What does this mean? Is there a proxy handling the requests that go in/out?

My best guess is, even though the CDN is setup to allow all domains at the moment, it may be rejecting requests due to a lack of referrer.

[jjborland]

I am using MC Visual Studio, and when testing, VS uses IIS locally as the web server. As far as I know, there are no proxies set up purposely within VS or my local machine for any reasons.