Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Customizing ASP.NET Core 6.0 - Second Edition

You're reading from  Customizing ASP.NET Core 6.0 - Second Edition

Product type Book
Published in Dec 2021
Publisher Packt
ISBN-13 9781803233604
Pages 204 pages
Edition 2nd Edition
Languages
Author (1):
Jürgen Gutsch Jürgen Gutsch
Profile icon Jürgen Gutsch
Toc

Table of Contents (18) Chapters close

Preface 1. Chapter 1: Customizing Logging 2. Chapter 2: Customizing App Configuration 3. Chapter 3: Customizing Dependency Injection 4. Chapter 4: Configuring and Customizing HTTPS with Kestrel 5. Chapter 5: Configuring WebHostBuilder 6. Chapter 6: Using Different Hosting Models 7. Chapter 7: Using IHostedService and BackgroundService 8. Chapter 8: Writing Custom Middleware 9. Chapter 9: Working with Endpoint Routing 10. Chapter 10: Customizing ASP.NET Core Identity 11. Chapter 11: Configuring Identity Management 12. Chapter 12: Content Negotiation Using a Custom OutputFormatter 13. Chapter 13: Managing Inputs with Custom ModelBinder 14. Chapter 14: Creating a Custom ActionFilter 15. Chapter 15: Working with Caches 16. Chapter 16: Creating Custom TagHelper 17. Other Books You May Enjoy

Chapter 4: Configuring and Customizing HTTPS with Kestrel

In ASP.NET Core, HTTPS is on by default, and it is a first-class feature. On Windows, the certificate that is needed to enable HTTPS is loaded from the Windows certificate store. If you create a project on Linux or Mac, the certificate is loaded from a certificate file.

Even if you want to create a project to run it behind an IIS or an NGINX web server, HTTPS is enabled. Usually, you would manage the certificate on the IIS or NGINX web server in that case. Having HTTPS enabled here shouldn't be a problem, however, so don't disable it in the ASP.NET Core settings.

Managing the certificate within the ASP.NET Core application directly makes sense if you run services behind the firewall, services that are not accessible from the internet, services such as background services for a microservice-based application, or services in a self-hosted ASP.NET Core application.

There are also some scenarios on Windows where...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}