Always a SessionClose after a Cache Hit

[Bruce Rudolph]

Running Varnish 3.0.3 on CentOS 5.8.

I am wondering why there is a SessionClose after a cache hit and delivery. The example below shows the varnishlog output of the request/response. There is a keep-alive header in the request and response. Normally the client calling my app would still keep the session open and is supposed to send more requests.

Any suggestions?

10773 SessionOpen  c 204.13.194.63 53590 :80
10773 ReqStart     c 204.13.194.63 53590 134881832
10773 RxRequest    c GET
10773 RxURL        c /ourapp?url=http%3A%2F%2Fjsonline.com
10773 RxProtocol   c HTTP/1.1
10773 RxHeader     c Host: 8.12.230.136
10773 RxHeader     c Connection: keep-alive
10773 VCL_call     c recv lookup
10773 VCL_call     c hash
10773 Hash         c jsonline.com
10773 VCL_return   c hash
10773 Hit          c 134858969
10773 VCL_call     c hit deliver
10773 VCL_call     c deliver deliver
10773 TxProtocol   c HTTP/1.1
10773 TxStatus     c 200
10773 TxResponse   c OK
10773 TxHeader     c Cache-Control: s-maxage=86400
10773 TxHeader     c Content-Type: text/plain
10773 TxHeader     c Content-Length: 13
10773 TxHeader     c Accept-Ranges: bytes
10773 TxHeader     c Date: Thu, 18 Apr 2013 19:55:17 GMT
10773 TxHeader     c X-Varnish: 134881832 134858969
10773 TxHeader     c Age: 10
10773 TxHeader     c Via: 1.1 varnish
10773 TxHeader     c Connection: keep-alive
10773 Length       c 13
10773 ReqEnd       c 134881832 1366314917.734391928 1366314917.734510899 1.976155043 0.000053167 0.000065804
10773 SessionClose c EOF


Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20130418/5c2ed566/attachment.html>