Book Image

ASP.NET Core MVC 2.0 Cookbook

By : Jason De Oliveira, Engin Polat, Stephane Belkheraz
Book Image

ASP.NET Core MVC 2.0 Cookbook

By: Jason De Oliveira, Engin Polat, Stephane Belkheraz

Overview of this book

The ASP.NET Core 2.0 Framework has been designed to meet all the needs of today’s web developers. It provides better control, support for test-driven development, and cleaner code. Moreover, it’s lightweight and allows you to run apps on Windows, OSX and Linux, making it the most popular web framework with modern day developers. This book takes a unique approach to web development, using real-world examples to guide you through problems with ASP.NET Core 2.0 web applications. It covers Visual Studio 2017- and ASP.NET Core 2.0-specifc changes and provides general MVC development recipes. It explores setting up .NET Core, Visual Studio 2017, Node.js modules, and NuGet. Next, it shows you how to work with Inversion of Control data pattern and caching. We explore everyday ASP.NET Core MVC 2.0 patterns and go beyond it into troubleshooting. Finally, we lead you through migrating, hosting, and deploying your code. By the end of the book, you’ll not only have explored every aspect of ASP.NET Core MVC 2.0, you’ll also have a reference you can keep coming back to whenever you need to get the job done.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Introduction


In this section, we will take a look at how authentication works in ASP.NET Core.

Note

All examples in this chapter can be found at https://github.com/polatengin/B05277/tree/master/Chapter17 GitHub repo.

The HTTP protocol is a stateless, response-for-a-request based protocol. This means an HTTP server can generate a response once it gets a request, and it never remembers previous requests and their results. Every request is processed separately.

For example, if an application requires you to log in first, a developer should handle the required logic flow to redirect to the user login page if they haven't logged in yet.

So, every request should have all the information to be processed successfully (if a user has logged in or not, who the user is, and their permissions.)

If a bad user sits on the line between the client and the server, they can read packages and easily pretend to be someone else.

Most of the server-side frameworks (ASP.NET, Java, Ruby, and so on) have some mechanism...