Http on random thoughts

Understanding HTTP/1.1: Redirects in Go (Part 3)

Sat, 25 Jan 2025 00:00:00 +0000

When I first learned about HTTP redirects I was confused about them. Which one do I need? One good way to always start from is the MDN Docs for any web standard related questions.

Read the docs and you don’t even need to read this at all. Bye. Or you can stay…

TL;DR

301 is permanent redirect. So if you hit it once the browser will cache it and won’t bother to reach out to the server for subsequent requests. On the other hand 302 won’t be cached and browser will hit our server every time user requests one of the urls. Same goes for 308 and 307. But they’ll preserve the HTTP method. There’s a nice table for that in MDN Docs.

Understanding HTTP/1.1: Content-Type in Go (Part 2)

Sat, 28 Dec 2024 00:00:00 +0000

Previously we’ve seen how to construct basic HTTP request and response with our simple TCP server. In this blog post we’ll go a bit deeper into the Content-Type header and see Content-Type in action.

This is specifically HTTP thing. So when we’re sending data to an HTTP client we can specify what type of data we’re sending by using a header called Content-Type. When the client is browser even if we don’t say the content type in header sometimes it’ll guess from the bytes sent to it. All these we’ll see in this blog post!

Understanding HTTP/1.1: TCP Server in Go (Part 1)

Thu, 12 Dec 2024 00:00:00 +0000

The goal of this blog post is to spin up a TCP server and start sending requests to the server with various clients. That way we’ll see what type of data an HTTP client like curl sends to the server. Out of all the versions of HTTP, we’ll focus on HTTP 1.x. As it’s a text based protocol and we’ll be able to see what’s going on under the hood.