<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tcp on random thoughts</title><link>https://riad.run/tags/tcp/</link><description>Recent content in Tcp on random thoughts</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 28 Dec 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://riad.run/tags/tcp/feed.xml" rel="self" type="application/rss+xml"/><item><title>Understanding HTTP/1.1: Content-Type in Go (Part 2)</title><link>https://riad.run/posts/http11-content-type/</link><pubDate>Sat, 28 Dec 2024 00:00:00 +0000</pubDate><guid>https://riad.run/posts/http11-content-type/</guid><description>&lt;p&gt;Previously we&amp;rsquo;ve seen how to construct basic HTTP request and response with our simple TCP server. In this blog post we&amp;rsquo;ll go a bit deeper into the &lt;code&gt;Content-Type&lt;/code&gt; header and see Content-Type in action.&lt;/p&gt;&#10;&lt;p&gt;This is specifically HTTP thing. So when we&amp;rsquo;re sending data to an HTTP client we can specify what type of data we&amp;rsquo;re sending by using a header called &lt;code&gt;Content-Type&lt;/code&gt;. When the client is browser even if we don&amp;rsquo;t say the content type in header sometimes it&amp;rsquo;ll guess from the bytes sent to it. All these we&amp;rsquo;ll see in this blog post!&lt;/p&gt;</description></item><item><title>Understanding HTTP/1.1: TCP Server in Go (Part 1)</title><link>https://riad.run/posts/http11tcpserver/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://riad.run/posts/http11tcpserver/</guid><description>&lt;p&gt;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&amp;rsquo;ll see what type of data an HTTP client like &lt;code&gt;curl&lt;/code&gt; sends to the server. Out of all the versions of HTTP, we&amp;rsquo;ll focus on &lt;code&gt;HTTP 1.x&lt;/code&gt;. As it&amp;rsquo;s a text based protocol and we&amp;rsquo;ll be able to see what&amp;rsquo;s going on under the hood.&lt;/p&gt;</description></item></channel></rss>