Connection storm under browser traffic causes instability and quota burn

[ghostlatency]

Use Case / مورد استفاده

Under browser-heavy workloads (especially YouTube / Brave / Safari with many tabs), the client can rapidly create hundreds of simultaneous sessions.

This eventually leads to instability even when endpoints themselves are healthy.

Observed symptoms:

• massive session growth
• repeated RST from server
• HTTP2 connection loss
• TLS handshake timeout
• Apps Script quota burning much faster during storms

Proposed Logic / منطق پیشنهادی

Add an optional connection/session storm protection mechanism.

Possible approaches:

• configurable max_active_sessions
• adaptive session limiting
• smarter browser connection coalescing
• optional per-domain throttling

Alternatives Considered / گزینه‌های جایگزین

Example config:

{
"max_active_sessions": 120
}

Visuals / Mockups / طرح‌ها یا دیاگرام‌ها

Real example from logs:

active=343
sessions=1198/855
polls=1351
rst=69

and later:

http2: client connection lost
TLS handshake timeout
shutdown: sending RST for 362 active sessions

This behavior is reproducible with:

• Brave browser
• YouTube traffic
• many open tabs
• Safari background traffic

Endpoints themselves remain healthy during many of these storms, suggesting the issue is mainly concurrent session explosion.