Book Image

ASP.NET Core 2 and Vue.js

By : Stuart Ratcliffe
5 (1)
Book Image

ASP.NET Core 2 and Vue.js

5 (1)
By: Stuart Ratcliffe

Overview of this book

This book will walk you through the process of developing an e-commerce application from start to finish, utilizing an ASP.NET Core web API and Vue.js Single-Page Application (SPA) frontend. We will build the application using a featureslice approach, whereby in each chapter we will add the required frontend and backend changes to complete an entire feature. In the early chapters, we’ll keep things fairly simple to get you started, but by the end of the book, you’ll be utilizing some advanced concepts, such as server-side rendering and continuous integration and deployment. You will learn how to set up and configure a modern development environment for building ASP.NET Core web APIs and Vue.js SPA frontends.You will also learn about how ASP.NET Core differs from its predecessors, and how we can utilize those changes to our benefit. Finally, you will learn the fundamentals of building modern frontend applications using Vue.js, as well as some of the more advanced concepts, which can help make you more productive in your own applications in the future.
Table of Contents (15 chapters)

Adding refresh token support to the frontend

We have now discussed the basic flow of how refresh tokens work, as well as implementing a means of performing that flow by adding an additional API endpoint to our server. All that remains is deciding how we actually modify the frontend of the application to automatically handle our refresh token flow without letting the user know what's happening.

We know that we need to watch every API call for a 401 HTTP status code response and attempt to obtain a new access token by hitting the refresh token API endpoint. We also know that we don't want to be doing this manually on every API request in the system, as it would be completely impractical to try and maintain them if the logic ever changed. We need a way of defining this logic in a single place and have it automatically work any time we add new API requests in the future...