Finally, HTTPS gets into ASP.NET Core. It was there before back in 1.1, but was kinda tricky to configure. It was available in 2.0 bit not configured by default. Now it is part of the default configuration and pretty much visible and present to the developers who will create a new ASP.NET Core 2.1 project.

So the title of this blog post is pretty much misleading because you don’t need to configure HTTPS, because it already is configured. So let’s have a look how it is configured and how it can be customized. First, create a new ASP.NET Core 2.1 web application.

Source: DZone

Related Posts

How to Create Your First Angular Element

Working With the Ignite UI for Angular Toolbox Extension in Visual Studio Code

Debug JavaScript in Production With Source Maps

Comparing JavaScript Browser Automation Frameworks

What Makes Haskell Unique, Part 3

How to Stop Using Callbacks and Start Living