HTTP response headers provide additional information about the server's response to an HTTP request. These headers are essential for web developers and server administrators to ensure efficient and secure communication between clients and servers. In this blog post, we will discuss some of the most common HTTP response headers and provide example values for each header.

We have been using FastAPI along with the Test-Driven Development process to come up with an authentication system. Till now we can register to own a tiny application using a username and password. We are also able to generate a JWT token to be classified as a logged-in user. But there is no point in logging in until the logged-in user can do something privileged. In this iteration of the series, we'd see how to access a protected endpoint using FastAPI and JWT.

In the last couple of posts in TDD Auth with FastAPI series, we've been sustainably moved towards a web service that can let users register with the service. Now what? We have already done the easy part. The next part is to look at the authorization. This involves letting the user log in. And only give access to what they are authorized for. Let us look at the login part first.

In this post I have gone through and collected events related to HTTP and it's gradual development.

Are you lost between Handle, HandleFunc, and HandlerFunc? If the answer is yes then this post is for you. To understand these pretty well we need to be familiar with interafces. Although `interface` is just a keyword, it's confusing at first when you are switching from Python like language; which does not have a similar keyword.