In ATS 7, with https requests, we are able to consistently reproduce clients getting disconnected at proxy.config.http.transaction_no_activity_timeout_in
for cache misses. eg when set to 20 we see:
$ curl --limit-rate 10M -D- https://example.com/mybigfile
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0HTTP/1.1 200 OK
Date: Fri, 30 Jun 2017 21:29:12 GMT
Last-Modified: Wed, 26 Oct 2016 22:24:18 GMT
Accept-Ranges: bytes
Content-Type: binary/octet-stream
Content-Length: 1125156837
Server: ATS/7.0.0
Cache-Control: max-age=600, public
Access-Control-Allow-Origin: *
Etag: "11c8b7ebe78d6a7bbacd4582820939f4"
Age: 0
Connection: close
18 1073M 18 203M 0 0 9.9M 0 0:01:47 0:00:20 0:01:27 10.0M
curl: (18) transfer closed with 904329920 bytes remaining to read
(note the 0:00:20 in the curl progress note)
or when set to 60
$curl --limit-rate 10M -D- https://example.com/mybigfile
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0HTTP/1.1 200 OK
Date: Fri, 30 Jun 2017 21:18:25 GMT
Last-Modified: Wed, 26 Oct 2016 22:24:18 GMT
ETag: "11c8b7ebe78d6a7bbacd4582820939f4"
Accept-Ranges: bytes
Content-Type: binary/octet-stream
Content-Length: 1125156837
Server: ATS/7.0.0
Cache-Control: max-age=600, public
Access-Control-Allow-Origin: *
Age: 2
Connection: close
59 1073M 59 638M 0 0 9.9M 0 0:01:47 0:01:03 0:00:44 10.0Mcurl: (18) transfer closed with 450919099 bytes remaining to read
(note the 0:01:03 in the curl progress note)
We could not reproduce the issue when serving from cache -- only for misses. Similarly, we can only reproduce with https requests, not http.
In ATS 7, with https requests, we are able to consistently reproduce clients getting disconnected at proxy.config.http.transaction_no_activity_timeout_in
for cache misses. eg when set to 20 we see:
(note the 0:00:20 in the curl progress note)
or when set to 60
(note the 0:01:03 in the curl progress note)
We could not reproduce the issue when serving from cache -- only for misses. Similarly, we can only reproduce with https requests, not http.