<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Headers on cloudmato.com</title><link>https://cloudmato.com/tags/headers/</link><description>Recent content in Headers on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Mon, 08 Jun 2026 00:25:52 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/headers/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding Common HTTP Headers on Amazon</title><link>https://cloudmato.com/posts/understanding-common-http-headers-on-amazon/</link><pubDate>Mon, 08 Jun 2026 00:25:52 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/understanding-common-http-headers-on-amazon/</guid><description>&lt;p&gt;Every request you make to a website carries a small pile of metadata you never see. Headers. They decide whether your connection is encrypted, whether a page can be embedded in an iframe, which CDN edge served you, and whether the browser should remember a cookie for a year. I wanted to see what a real, busy production site sends, so I pointed &lt;code&gt;curl&lt;/code&gt; at an Amazon endpoint and dumped the response headers. Turns out there&amp;rsquo;s a lot to unpack.&lt;/p&gt;</description></item></channel></rss>