<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>tomcat on </title>
    <link>/tags/tomcat/</link>
    <description>Recent content in tomcat on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 03 Jul 2026 00:20:00 +0800</lastBuildDate><atom:link href="/tags/tomcat/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Intermittent 413s Behind Spring Cloud Gateway: Anatomy of an h2c Upgrade Trap</title>
      <link>/posts/spring-cloud-gateway-413-h2c-upgrade/</link>
      <pubDate>Fri, 03 Jul 2026 00:20:00 +0800</pubDate>
      
      <guid>/posts/spring-cloud-gateway-413-h2c-upgrade/</guid>
      <description>The symptom A production mystery: file uploads through a Spring Cloud Gateway (Server MVC, servlet stack) — POST /api/file/upload, multipart/form-data — behaved like this:
With 1 gateway pod: 413 never happens;
Scaled to 3 gateway pods: intermittent 413 PAYLOAD_TOO_LARGE, gateway log:
&amp;#34;logger&amp;#34;: &amp;#34;o.s.web.servlet.DispatcherServlet&amp;#34;, &amp;#34;message&amp;#34;: &amp;#34;Completed 413 PAYLOAD_TOO_LARGE&amp;#34; Scale back to 1 pod, problem disappears;
The gateway was freshly deployed and its pods homogeneous; the upload backend ran 3 pods, also homogeneous.</description>
    </item>
    
  </channel>
</rss>
