Ability to launch HTTPS (SSL) URL #615

New Issue

claunia · 2026-01-29T16:44:09Z

claunia commented

2026-01-29 16:44:09 +00:00

Originally created by @jcb871 on GitHub (Jan 12, 2021).

Originally assigned to: @GregorBiswanger on GitHub.

Though the Electron.NET provides option to configure the port number to launch, it seems like http://localhost is hardcoded in Electron.NET. Could you please add an option to configure Electron.NET to launch the ASP.NET Core app with HTTPS URL?

I am developing a Blazor app with built-in Grpc service. It requires the service/web app to run in SSL mode (https URL) in order to consume from the web app.

This is asked in Gitter also but did not see that is answered. Please let me know if you can provide any pointers.

Originally created by @jcb871 on GitHub (Jan 12, 2021). Originally assigned to: @GregorBiswanger on GitHub. Though the Electron.NET provides option to configure the port number to launch, it seems like http://localhost is hardcoded in Electron.NET. Could you please add an option to configure Electron.NET to launch the ASP.NET Core app with HTTPS URL? I am developing a Blazor app with built-in Grpc service. It requires the service/web app to run in SSL mode (https URL) in order to consume from the web app. This is asked in Gitter also but did not see that is answered. Please let me know if you can provide any pointers.

claunia added the Feature label 2026-01-29 16:44:09 +00:00

claunia closed this issue

2026-01-29 16:44:10 +00:00

claunia commented

2026-01-29 16:44:11 +00:00

@mxmissile commented on GitHub (Feb 5, 2021):

I might be missing something, but this works for me:

Task.Run(async () => await Electron.WindowManager.CreateWindowAsync(loadUrl:"https://google.com"));

@mxmissile commented on GitHub (Feb 5, 2021): I might be missing something, but this works for me: `Task.Run(async () => await Electron.WindowManager.CreateWindowAsync(loadUrl:"https://google.com"));`

claunia commented

2026-01-29 16:44:12 +00:00

@FlorianRappl commented on GitHub (Nov 1, 2025):

In my opinion that is not a feature we'd bring in. Since the application is running on localhost / inside the app you will need a self-signed certificate. To have this the Chromium engine would complain or we would need to handle SSL errors.

While I think we could have an option to do this (= ignore certificate errors), it would bring a potential security risk (this way also connections to the outside would not be checked). In conclusion, I see the risk much higher than the value.

@FlorianRappl commented on GitHub (Nov 1, 2025): In my opinion that is not a feature we'd bring in. Since the application is running on localhost / inside the app you will need a self-signed certificate. To have this the Chromium engine would complain or we would need to handle SSL errors. While I think we could have an option to do this (= ignore certificate errors), it would bring a potential security risk (this way also connections to the outside would not be checked). In conclusion, I see the risk much higher than the value.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#615