[squid-users] TCP_REFRESH_MODIFIED

[joe]

hi amos  
this is the header
Connection: keep-alive

HTTP/1.1 200 OK
Last-Modified: Mon, 02 Nov 2015 08:13:05 GMT
Content-Type: video/mp4
Date: Tue, 03 Nov 2015 18:25:03 GMT
Expires: Tue, 03 Nov 2015 18:25:03 GMT
Cache-Control: private, max-age=21297
Accept-Ranges: bytes
Content-Length: 131072
access-control-allow-origin: #######################
Access-Control-Allow-Credentials: true
Timing-Allow-Origin: #############################
Access-Control-Expose-Headers: Client-Protocol, Content-Length, Content-Type
x-content-type-options: nosniff
Server: gvs 1.0
Age: 5297   
sorry for not providing the url  no need i gess but 
as you see 
Content-Length: 131072  same  and all other info in header same never change 
i the only person on that cache no other clients  its my test bansh
i dont hit re load at all  just passing the link click go  after 30 or more
minut 
somtime less right after  just click refresh botton no ctl F5  
age ar ok shuld stay in cache for that amount lets say 
Cache-Control: private, max-age=21297    i had in refresh pattern 
367840  99% 535600 override-expire override-lastmod ignore-reload
ignore-no-store ignore-private reload-into-ims store-stale 
and it cache it np with that  but why it look like care without brake lol 
TCP_REFRESH_MODIFIED
or swap fail
but mostly MODIFIED  and its not
unless override-expire override-lastmod ignore-reload ignore-no-store
ignore-private  bit ar unset some how 



--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674327.html
Sent from the Squid - Users mailing list archive at Nabble.com.