<?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 ilham.dev</title><link>https://ilham.dev/tags/headers/</link><description>Recent content in Headers on ilham.dev</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0700</lastBuildDate><atom:link href="https://ilham.dev/tags/headers/index.xml" rel="self" type="application/rss+xml"/><item><title>How I build an HTTP header block without forgetting security headers</title><link>https://ilham.dev/posts/how-to-build-an-http-header-block/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-build-an-http-header-block/</guid><description>Building headers from key/value rows helps avoid typo-heavy manual header blocks.
I use HTTP Header Builder for the quick version of this task, then I review the output before relying on it.</description></item><item><title>How I read email headers when a message looks suspicious</title><link>https://ilham.dev/posts/how-to-read-email-headers/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-read-email-headers/</guid><description>An email header is the technical history of a message. It can show where the message claimed to come from, which servers handled it, and whether authentication checks passed.
The visible email body can be misleading.</description></item><item><title>How I read HTTP headers when an API or website behaves strangely</title><link>https://ilham.dev/posts/how-to-read-http-headers/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-read-http-headers/</guid><description>HTTP headers are small pieces of metadata sent with a request or response. They can explain things that are not visible in the page body.
When a website or API behaves strangely, I often look at the headers first.</description></item></channel></rss>