web: raise the /v1 rewrite proxy timeout to 180 s (browser renders + captcha solving)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1 changed file +3 −0
modified
apps/web/next.config.ts
+3 −0
@@ -8,6 +8,9 @@ const nextConfig: NextConfig = { | ||
| 8 | 8 | poweredByHeader: false, |
| 9 | 9 | transpilePackages: ["@fetcha/core", "@fetcha/db", "@fetcha/email", "@fetcha/providers"], |
| 10 | 10 | serverExternalPackages: ["pg", "undici", "resend"], |
| 11 | + // Browser renders + captcha solving can legitimately take 60–120 s: the default 30 s rewrite proxy | |
| 12 | + // timeout would answer 500 before the API replies. | |
| 13 | + experimental: { proxyTimeout: 180_000 }, | |
| 11 | 14 | async rewrites() { |
| 12 | 15 | // Public API is served on the same domain under /v1/* and forwarded to the Fastify service. |
| 13 | 16 | return [ |
| 14 | 17 | |