Domain fronting relay (for non-Telegram traffic) had no idle timeout, causing worker pool exhaustion under traffic spikes. The ProxyOpts.IdleTimeout field existed but was never wired into the proxy. Now domain fronting connections are wrapped with per-read/write deadlines reset to the configured idle timeout (default 1m), so stale or slowloris-style connections are reaped promptly. Fixes #378tags/v2.2.5^2^2
|
|
||
| 262 |
|
262 |
|
| 263 |
|
263 |
|
| 264 |
|
264 |
|
|
265 |
|
|
| 265 |
|
266 |
|
| 266 |
|
267 |
|
| 267 |
|
268 |
|
|
|
||
| 6 |
|
6 |
|
| 7 |
|
7 |
|
| 8 |
|
8 |
|
|
9 |
|
|
| 9 |
|
10 |
|
| 10 |
|
11 |
|
| 11 |
|
12 |
|
|
|
||
| 95 |
|
96 |
|
| 96 |
|
97 |
|
| 97 |
|
98 |
|
|
99 |
|
|
|
100 |
|
|
|
101 |
|
|
|
102 |
|
|
|
103 |
|
|
|
104 |
|
|
|
105 |
|
|
|
106 |
|
|
|
107 |
|
|
|
108 |
|
|
|
109 |
|
|
|
110 |
|
|
|
111 |
|
|
|
112 |
|
|
|
113 |
|
|
|
114 |
|
|
|
115 |
|
|
|
116 |
|
|
|
||
| 27 |
|
27 |
|
| 28 |
|
28 |
|
| 29 |
|
29 |
|
|
30 |
|
|
| 30 |
|
31 |
|
| 31 |
|
32 |
|
| 32 |
|
33 |
|
|
|
||
| 306 |
|
307 |
|
| 307 |
|
308 |
|
| 308 |
|
309 |
|
| 309 |
|
|
|
| 310 |
|
|
|
|
310 |
|
|
|
311 |
|
|
| 311 |
|
312 |
|
| 312 |
|
313 |
|
| 313 |
|
314 |
|
|
|
||
| 339 |
|
340 |
|
| 340 |
|
341 |
|
| 341 |
|
342 |
|
|
343 |
|
|
| 342 |
|
344 |
|
| 343 |
|
345 |
|
| 344 |
|
346 |
|
|
|
||
| 216 |
|
216 |
|
| 217 |
|
217 |
|
| 218 |
|
218 |
|
|
219 |
|
|
|
220 |
|
|
|
221 |
|
|
|
222 |
|
|
|
223 |
|
|
|
224 |
|
|
|
225 |
|
|
|
226 |
|
|
| 219 |
|
227 |
|
| 220 |
|
228 |
|
| 221 |
|
229 |
|