If you have a Blazor Front-End and add a "Facade Rest proxy" he will create the according classes which will utilize the RootServiceUrl setting to access the proxy. This setting does not initially exists in the wwwroot/appsettings.Development.json , settings section _Blazor.OAuth2.Frontend_Project_Name.FrontEnd.Settings_
You have to add it manually and set it to the URL and port of the proxy.
I -as absolute guidance beginner- tried to fix this initially by adding this setting with the value of the back ends port not the proxies port (https://localhost:723**9/ instead of https://localhost:7238**/), leading to some security related exceptions/erros (as far as I remember).
Desired solution
Initially adding this setting to the proxies URL in the appsettings.Development.json of the frontends wwwroot/appsettings.Development.json would ease the initial creation for new developers.
Problem
If you have a Blazor Front-End and add a "Facade Rest proxy" he will create the according classes which will utilize the RootServiceUrl setting to access the proxy. This setting does not initially exists in the wwwroot/appsettings.Development.json , settings section _Blazor.OAuth2.Frontend_Project_Name.FrontEnd.Settings_ You have to add it manually and set it to the URL and port of the proxy. I -as absolute guidance beginner- tried to fix this initially by adding this setting with the value of the back ends port not the proxies port (https://localhost:723**9/ instead of https://localhost:7238**/), leading to some security related exceptions/erros (as far as I remember).
Desired solution
Initially adding this setting to the proxies URL in the appsettings.Development.json of the frontends wwwroot/appsettings.Development.json would ease the initial creation for new developers.