<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Http on Ou David | Systems Engineer</title><link>https://preview.vvivid.dev/tags/http/</link><description>Recent content in Http on Ou David | Systems Engineer</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 08 Aug 2025 10:00:00 +0000</lastBuildDate><atom:link href="https://preview.vvivid.dev/tags/http/index.xml" rel="self" type="application/rss+xml"/><item><title>The HTTP Request Journey in Go: From Network to Handler</title><link>https://preview.vvivid.dev/posts/http_in_golang/</link><pubDate>Fri, 08 Aug 2025 10:00:00 +0000</pubDate><guid>https://preview.vvivid.dev/posts/http_in_golang/</guid><description>&lt;p&gt;As a backend guy, I&amp;rsquo;ve been tasked with building various APIs for different projects, and most of them I built using Go. For the majority of the time, what most people do is write a handler or middleware to process and respond to requests. Today, we&amp;rsquo;re going to do something different. We&amp;rsquo;ll go down a rabbit hole together into the abstractions that Go has taken away from us. We&amp;rsquo;ll see all the interesting things that Go does before handing us the request and response objects in our handler. After this deep dive, we&amp;rsquo;ll understand how to parse requests, how routing matching works, middleware execution, and finally the architecture that Go uses to handle each request.&lt;/p&gt;</description></item></channel></rss>