Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By : Jürgen Gutsch
Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By: Jürgen Gutsch

Overview of this book

ASP.NET Core is packed full of hidden features for building sophisticated web applications – but if you don’t know how to customize it, you’re not making the most of its capabilities. Customizing ASP.NET Core 6.0 is a book that will teach you all about tweaking the knobs at various layers and take experienced programmers’ skills to a new level. This updated second edition covers the latest features and changes in the .NET 6 LTS version, along with new insights and customization techniques for important topics such as authentication and authorization. You’ll also learn how to work with caches and change the default behavior of ASP.NET Core apps. This book will show you the essential concepts relating to tweaking the framework, such as configuration, dependency injection, routing, action filters, and more. As you progress, you'll be able to create custom solutions that meet the needs of your use case with ASP.NET Core. Later chapters will cover expert techniques and best practices for using the framework for your app development needs, from UI design to hosting. Finally, you'll focus on the new endpoint routing in ASP.NET Core to build custom endpoints and add third-party endpoints to your web apps for processing requests faster. By the end of this book, you'll be able to customize ASP.NET Core to develop better, more robust apps.
Table of Contents (18 chapters)

Caching using ResponseCachingMiddleware

The ResponseCachingMiddleware caches the responses on the server side and creates responses based on the cached responses. The middleware respects the Cache-Control header in the same way as clients do. That means you are able to control the middleware by setting the specific headers as described in the previews section.

To get it working you need to add the ResponseCachingMiddleware to the Dependency Injection container:

builder.Services.AddResponseCaching();

And you should use that middleware to the pipeline after the static files and routing got added:

app.UseResponseCaching();

If you added a CORS configuration, the UseCors method should be called before, as well.

The ResponseCachingMiddleware gets affected by specific HTTP headers. For example, if the Authentication header is set the response doesn't get cached, same with the Set-Cookie header. It also only caches responses that result in a 200 OK result. Error pages...