[Bug] Vite dev server fails to load socket:* due to CORS

[rorymcd98]

[Bug] Vite dev server fails to load socket:* due to CORS

[jwerle]

I tried your repo on my macOS machine and it seems to work there. I'll try again later on my Windows machine and report back.

[rorymcd98]

@jwerle thanks I'll try again later on another windows intel machine.

[rorymcd98]

More info. It doesn't work on my other windows 11 machine (identical error log I believe).

It does work on Linux Fedora 39.

[jwerle]

@rorymcd98 okay! We'll dive in and figure this out

[rorymcd98]

Thanks - I'll work on Linux for now. Let me know if you need more info.

[garth]

I think I may have found the issue... I get CORS errors when running from a regular command prompt, but if when starting from a Visual Studio Command Prompt the CORS errors are gone and the app loads.

Update:

This only fixes the issue with a production build. Starting the app in development (with vite) still has CORS errors even though vite is configured to allow any origin.

[WolfBearGames]

I'm running into the same problem on Windows. It seems to work on Linux though.

Edit:
I tried to investigate the differences between Linux and Windows.
On Windows the request to "socket://internal/init" fails because the CORS headers are missing.
On Linux there does not seem to be CORS check, so the resource is requested responded correctly.

So, the webviews on Windows and Linux seem to handle the request differently.

Edit 2:
Running the app without the vite dev server ("ssc build -r") works. When using the context menu to reload the page one can the request to "socket://internal/init". In this case the request works and has response headers (Access-Control-Allow-Headers: * and Access-Control-Allow-Origin: *).