每次到15s左右就499

[feiye311]

每次到15s左右就499。

[github-actions]

Thank you for reporting this issue.

Analysis:

Based on my analysis of the codebase, the 499 status code indicates Client Closed Request - the client terminated the connection before the server could complete the response.

About the 15-second timeout:

The 15-second timeout you're experiencing is likely coming from outside the CCH proxy server:

1. CCH timeout defaults (from src/drizzle/schema.ts):

   • firstByteTimeoutStreamingMs: 0 (no limit, by default)
   • streamingIdleTimeoutMs: 0 (no limit, by default)
   • requestTimeoutNonStreamingMs: 0 (no limit, by default)
   • Global fetch timeouts: 600 seconds

2. The 15-second timeout is likely from:

   • Your client (SDK, API tool, browser) configured with a 15s timeout
   • A reverse proxy/load balancer in front of CCH (e.g., nginx, Cloudflare)
   • A network device/firewall with a 15-second connection timeout

Possible causes:

1. Provider slow first-byte: The upstream provider is taking too long to send the first byte of the response
2. Network issues: Latency between your client and the CCH server
3. Reverse proxy timeout: If you're using nginx or similar, check proxy_read_timeout or proxy_connect_timeout

Diagnostic steps:

1. Check the decision chain (决策链) in the dashboard for the affected requests - this will show the actual timing and error details
2. Verify your client's timeout configuration
3. If using a reverse proxy, check its timeout settings
4. Check if specific providers have firstByteTimeoutStreamingMs configured in the database

Configuration options:

If the upstream provider is slow, you can configure per-provider timeouts in the provider settings:

• firstByteTimeoutStreamingMs: Controls timeout for first byte in streaming requests
• streamingIdleTimeoutMs: Controls timeout for silent periods during streaming

Could you share:

1. Which client you're using (SDK version, API tool, etc.)
2. Whether you're using a reverse proxy/load balancer in front of CCH
3. A screenshot of the decision chain (决策链) for a failed request

This will help identify the exact source of the 15-second timeout.

---

Automated response from Claude AI

[tesgth032]

499 是下游主动断开连接，请检查下游网关（如果有）和客户端侧的超时设置