Documentation:LocalhostDevCert: Difference between revisions

LocalhostDevCert

Revision as of 07:51, 7 February 2023

Note: From 210405 Turnkey core and MDrivenServer core, allow for HTTP access by sending in parameter - no HTTPS as described here: LocalServers

To let the server talk over SSL without security warnings, there must exist SSL-certificates for localhost:PortNo.

This is what is typically called a Developer Certificate.

In order to register the developer-SSL cert, you must have the .netCore SDK installed.

If you already have it, jump to step 2.

dotnet dev-certs https --trust

If you suspect that there is something wrong, try to clean it first:

dotnet dev-certs https --clean
dotnet dev-certs https --trust

This page was edited 98 days ago on 02/10/2024. What links here

@@ Line 1: / Line 1: @@
-'''Note:''' From 210405 Turnkey core and MDrivenServer core allow for http access by sending in parameter -nohttps as described here [[LocalServers]]
+'''Note:''' From 210405 Turnkey core and MDrivenServer core, allow for HTTP access by sending in parameter - no HTTPS as described here: [[LocalServers]]
-In order to let the server talk over SSL without security warnings there must exists ssl-certificates for localhost:PortNo.
+To let the server talk over SSL without security warnings, there must exist SSL-certificates for localhost:PortNo.
 This is what is typically called a Developer Certificate.
-In order to register the developer-ssl cert you must have the .netCore SDK installed.
+In order to register the developer-SSL cert, you must have the .netCore SDK installed.
-If you have it already jump to step 2.
+If you already have it, jump to step 2.
 # Download the .netCore3.1 SDK https://dotnet.microsoft.com/download/dotnet-core/thank-you/sdk-3.1.404-windows-x64-installer and install it.
-# In a cmd window paste this and press enter:
+# In a cmd window, paste this and press enter:
   dotnet dev-certs https --trust
-If you suspect that there is something wrong try to clean it first:
+If you suspect that there is something wrong, try to clean it first:
   dotnet dev-certs https --clean
   dotnet dev-certs https --trust
-[[Category:MDriven Turnkey]]
+ [[Category:MDriven Turnkey]]
-[[Category:MDriven Server]]
+ [[Category:MDriven Server]]