<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Spring on After the Code</title><link>https://windshock.github.io/en/tags/spring/</link><description>Recent content in Spring on After the Code</description><generator>Hugo -- 0.145.0</generator><language>en-US</language><lastBuildDate>Tue, 25 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/en/tags/spring/index.xml" rel="self" type="application/rss+xml"/><item><title>Race Condition (TOCTOU) Remediation: What Actually Worked in a Real Stack</title><link>https://windshock.github.io/en/post/2026-08-25-race-condition-toctou-mitigation/</link><pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/en/post/2026-08-25-race-condition-toctou-mitigation/</guid><description>The same check-then-act race keeps appearing across services: purchase-limit bypass, one draw used by many requests, duplicate coupon cancellation, daily-reward overruns. I built a real stack (nginx + Tomcat×2 + shared Postgres + Redis) and measured which fix actually holds. Most of them need no Redis lock — just a DB conditional UPDATE and an affected-rows check.</description></item></channel></rss>