Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Customizing ASP.NET Core 5.0

You're reading from   Customizing ASP.NET Core 5.0 Turn the right screws in ASP.NET Core to get the most out of the framework

Arrow left icon
Product type Paperback
Published in Jan 2021
Publisher Packt
ISBN-13 9781801077866
Length 160 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Jürgen Gutsch Jürgen Gutsch
Author Profile Icon Jürgen Gutsch
Jürgen Gutsch
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Chapter 1: Customizing Logging 2. Chapter 2: Customizing App Configuration FREE CHAPTER 3. Chapter 3: Customizing Dependency Injection 4. Chapter 4: Configuring and Customizing HTTPS with Kestrel 5. Chapter 5: Using IHostedService and BackgroundService 6. Chapter 6: Writing Custom Middleware 7. Chapter 7: Content Negotiation Using a Custom OutputFormatter 8. Chapter 8: Managing Inputs with Custom ModelBinders 9. Chapter 9: Creating a Custom ActionFilter 10. Chapter 10: Creating Custom TagHelpers 11. Chapter 11: Configuring WebHostBuilder 12. Chapter 12: Using Different Hosting Models 13. Chapter 13: Working with Endpoint Routing 14. 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.

The endpoints are the parts of the 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 $19.99/month. Cancel anytime
Banner background image