<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Caddy on The Coders Blog</title><link>https://thecodersblog.com/tag/caddy/</link><description>Recent content in Caddy on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 09 May 2026 11:01:12 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/caddy/index.xml" rel="self" type="application/rss+xml"/><item><title>[Caddy]: High-Performance Web Serving</title><link>https://thecodersblog.com/caddy-web-server-enhancements-2026/</link><pubDate>Sat, 09 May 2026 11:01:12 +0000</pubDate><guid>https://thecodersblog.com/caddy-web-server-enhancements-2026/</guid><description>&lt;p&gt;Remember the days of meticulously crafting Nginx or Apache configuration files, wrestling with SSL certificate renewals, and praying for zero-downtime reloads? For many in the web development and DevOps world, that memory is still quite fresh. Then came Caddy, a web server that promised to simplify, secure, and accelerate the serving of web content. Far from being just a trendy newcomer, Caddy has matured into a formidable contender, quietly redefining what we expect from a modern, developer-friendly web server.&lt;/p&gt;</description></item></channel></rss>