<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>caching on Andrew Katsikas - Software Engineer</title>
    <link>https://katsikas-dev.newhellstudios.com/blog/caching/</link>
    <description>Recent content in caching on Andrew Katsikas - Software Engineer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>Copyright © 2023, Andrew Katsikas.</copyright>
    <lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://katsikas-dev.newhellstudios.com/blog/caching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What I learned about HTTP caching the hard way</title>
      <link>https://katsikas-dev.newhellstudios.com/what-i-learned-about-http-caching-the-hard-way/</link>
      <pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://katsikas-dev.newhellstudios.com/what-i-learned-about-http-caching-the-hard-way/</guid>
      <description>I run a self-hosted file-sharing service called slskd on a Raspberry Pi. After a routine update one day, a feature broke. The &amp;ldquo;Search for Additional Files in This Directory&amp;rdquo; function was returning errors. A hard refresh of the page fixed it immediately. I noted it was odd, moved on and forgot about it.
Then it happened again after using it on another device.
This time I dug in. The browser was running old JavaScript that referenced an API endpoint that had been removed in the new version.</description>
    </item>
    
  </channel>
</rss>
