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

Exploring endpoint routing

To learn about endpoint routing, you need to learn what an endpoint is and what routing is.

Endpoints are part of an app that get executed when a route maps the incoming request to it. Let's analyze this definition in a little more detail.

A client usually requests a resource from a server. In most cases, the client is a browser. The resource is defined by a URL, which points to a specific target. In most cases, the target is a web page. It could also be a mobile app that requests specific data from a JSON web API. What data the app requests is defined in the URL.

This means that the incoming request is also defined by the URL. The executing endpoint, on the other hand, is mapped to a specific route. A route is a URL or a pattern for a URL. ASP.NET Core developers are already familiar with such a route pattern:

app.UseRouting();
app.UseAuthorization();
app.UseEndpoints(endpoints =>
{
    endpoints.MapControllerRoute...
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}