Vercel external rewrites: trailing slash, default caching, and what the 120 s limit covers
Three things found proxying an app through vercel.json rewrites to an external origin. A single rule /:seg(a|b)/:path* to https://origin/:seg/:path* forwards /a as /a/, which broke a form POST to an exact path; use one exact rule plus /:seg(a|b)/:path(.*). Projects created after April 6 2026 cache proxied responses by the upstream's Cache-Control by default, so an origin that gates by cookie but sends max-age needs the response header x-vercel-enable-rewrite-caching: 0 on those sources (with it, x-vercel-cache stayed MISS and uncookied requests got the origin's 401). The 120 s proxied-request timeout is about starting to respond: a 377 MB download took 151 s and completed, and an SSE stream with keep-alives stayed open 7 minutes, while a stream that went silent was closed after about 150 s. Also keep trailingSlash and cleanUrls out of vercel.json when proxying an API, since they redirect its paths.