Golang 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.

Structured Logging in Go with log/slog

Thu, 14 Sep 2023 00:00:00 +0000

So you want to use the new shiny structured logging library in golang

log/slog#

slog (a structured logging library in Go) has been included in the Go standard library starting from version 1.21. While Go already had a logging library, it was considered too simple for most use cases. For starters, it lacked the leveled logging feature. To achieve leveled logging, you had to create multiple loggers with the level as a prefix and direct them all to the same io.Writer. This package, spf13/jwalterweatherman, accomplishes exactly that. There are also several third-party, excellent logging libraries available for structured logging, such as rs/zerolog, uber-go/zap, and sirupsen/logrus, to name a few. Now that structured logging is included in the standard library, let’s give it a try.

Trace Logging in Golang

Sun, 20 Aug 2023 00:00:00 +0000

Disclaimer: This article is not about runtime/trace package or trace profiling functionalities.

Tracing is used to observe code execution paths. If you log something in a function and you see that output in the log file, then you know that the function has been executed. There is a log level defined in different logger implementations called TRACE, which is the lowest log level in most loggers. The log won’t be present in the production environment, but when debugging, you’ll receive the traces. This is useful in situations where a debugger is not accessible.

Signal Handling and Graceful Shutdown in Go

Sat, 11 Mar 2023 00:00:00 +0000

All the code samples used in this post are available here.

Graceful Shutdown#

When a process is running for a long time, sometimes we want to quit the running program. If it’s a CLI process we press CTRL+C or send specific kill signals. For GUI applications we quit from the menu or if the process becomes nonresponsive we find the PID of the process and then run kill -9 <PID>. These actions trigger an event and the event is sent to the specific process which sometimes causes the process to exit. In a stateful program, we want to save the states or perform cleanups before exiting the process. This safe exit process is called graceful shutdown.

Symmetric Encryption with ChaCha20-Poly1305 in Go

Thu, 14 Jul 2022 00:00:00 +0000

This post is not completed yet

Recently, I’ve started learning cryptography and in general different cryptographic concepts. So this blog post is a documentation of the process. I’ve linked a book where you’ll be able to find most of it in great detail.

First, I want to recommend this book to any software developer. If you haven’t read this book yet, I highly recommend reading it. It contains most of the commonly used cryptographic concepts which I believe enable any developer to write secure code in any domain.