<?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 ilham.dev</title><link>https://ilham.dev/tags/http/</link><description>Recent content in Http 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/http/index.xml" rel="self" type="application/rss+xml"/><item><title>How I build a Basic Auth header for testing</title><link>https://ilham.dev/posts/how-to-build-a-basic-auth-header-for-testing/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-build-a-basic-auth-header-for-testing/</guid><description>Basic Auth sends a username and password encoded with Base64 inside an Authorization header. It is not encryption by itself.
The Basic Auth Header tool helps with the mechanical part, but I still check the result before using it somewhere real.</description></item><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 convert a curl command into code I can actually use</title><link>https://ilham.dev/posts/how-to-convert-curl-commands-into-code/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-convert-curl-commands-into-code/</guid><description>API documentation often gives examples as curl commands:
curl -X POST https://api.example.com/users \ -H &amp;#34;Authorization: Bearer TOKEN&amp;#34; \ -H &amp;#34;Content-Type: application/json&amp;#34; \ -d &amp;#39;{&amp;#34;name&amp;#34;:&amp;#34;Ana&amp;#34;}&amp;#39; That is useful for testing, but eventually I need the same request in application code.</description></item><item><title>How I look up HTTP status codes during debugging</title><link>https://ilham.dev/posts/how-to-look-up-http-status-codes-during-debugging/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-look-up-http-status-codes-during-debugging/</guid><description>HTTP status codes are short signals from a server. They tell me whether a request succeeded, redirected, failed on the client side, or failed on the server side.
The HTTP Status Codes tool helps me inspect the input and output without writing a one-off script first.</description></item><item><title>How I look up MIME types when uploads or downloads behave oddly</title><link>https://ilham.dev/posts/how-to-look-up-mime-types-for-files/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-look-up-mime-types-for-files/</guid><description>A MIME type tells software what kind of content a file or response contains.
The MIME Types tool helps with the mechanical part, but I still check the result before using it somewhere real.</description></item><item><title>How I read a curl command before I run it</title><link>https://ilham.dev/posts/how-to-read-a-curl-command-before-running-it/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-read-a-curl-command-before-running-it/</guid><description>A curl command is an HTTP request written for the terminal. Before running one from documentation or chat, I want to know what it will send.
The curl Tester tool gives me a safe place to test the idea before I put it into a script, server, or production workflow.</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><item><title>How I test an HTTP request before writing the code around it</title><link>https://ilham.dev/posts/how-to-test-an-http-request-before-writing-code/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-test-an-http-request-before-writing-code/</guid><description>Before I put an API call into code, I like to prove the request works by itself: URL, method, headers, body, and response.
The HTTP Request Tester tool gives me a safe place to test the idea before I put it into a script, server, or production workflow.</description></item></channel></rss>