[ https://issues.apache.org/jira/browse/TS-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Susan Hinrichs closed TS-2107. ------------------------------ Resolution: Won't Fix Fix Version/s: (was: sometime) Looking at restructuring stale connection recovery. That should eliminate the resource attack problem this issue is trying to address. > add absolute proxy.config.http.transaction_active_timeout_in about request > --------------------------------------------------------------------------- > > Key: TS-2107 > URL: https://issues.apache.org/jira/browse/TS-2107 > Project: Traffic Server > Issue Type: New Feature > Components: HTTP > Affects Versions: 3.3.5 > Reporter: Bin Chen > Assignee: Bin Chen > Attachments: TS-2107.patch > > > Now, ts use proxy.config.http.transaction_active_timeout_in handle request > and response transaction. But in some very bad network, we catch some log > that it cost >30s to get ua_read_header_done, that is unacceptable, should be > controled with some dedicated timeout in records.config. > we world prefer to add proxy.config.http.transaction_header_timeout_in > proxy.config.http.transaction_request_timeout_in > {code} > [Aug 6 22:11:46.698] Server {0x2b37cf0f9700} ERROR: [1366077161] Slow > Request: url: http://xxxxx/853771125_1448036722.jpg status: 0 unique id: > bytes: 0 fd: 0 client state: 0 server state: 0 ua_begin: 0.000 > ua_read_header_done: 46.790 cache_open_read_begin: 46.790 > cache_open_read_end: -1.000 dns_lookup_begin: -1.000 dns_lookup_end: -1.000 > server_connect: -1.000 server_first_read: -1.000 server_read_header_done: > -1.000 server_close: -1.000 ua_close: 46.790 sm_finish: 46.790 > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)