13 Middleware, HTTP routing, and HTTP responses

 

This chapter covers

  • Routing HTTP requests to controllers and endpoints
  • Declaring HTTP routes with HttpAttribute method attributes
  • Injecting dependencies with middleware
  • Using the IActionResult interface to return HTTP responses

We are almost at the end of our journey. In chapters gone by, we implemented the database access layer, the repository layer, and the service layer. Our service is almost implemented but not yet usable by FlyTomorrow (our client). To interact with our service, we need to provide controllers that accept HTTP requests and kick off the necessary processing.

In section 13.1, we’ll discuss the controller’s place within our repository/service architecture. Following that, in section 13.2, we’ll determine which controllers we need to implement. In the following sections, we’ll start to implement the FlightController (section 13.3) and explore how to route HTTP requests to our endpoints (section 13.4).

Figure 13.1 shows where are in the scheme of the book.

Figure 13.1 In the previous chapters, we implemented the database access, repository, and service layers. In this chapter, we’ll start to implement all controllers needed for our service.

13.1 The controller class within the repository/service pattern

13.2 Determining what controllers to implement

13.3 Implementing the FlightController

13.3.1 Returning HTTP responses with the IActionResult interface (GetFlights)

13.3.2 Injecting dependencies into a controller using middleware

13.3.3 Implementing the GET /Flight/{FlightNumber} endpoint

13.4 Routing HTTP requests to controllers and methods

Exercises

Summary