I'm setting icp_query_timeout 9000 because my cache peer is responding a little slowly and this setting was doing great job in squid 3.1, but after migrating in a test installation to 3.3 then again I started seeing in the ACCESS log
30/Jul/2013:15:12:54 +0530 28700 115.127.14.209 TCP_MISS/200 238022 GET http://r14---sn-cvh7zn7r.c.youtube.com/videoplayback? - TIMEOUT_FIRSTUP_PARENT/10.240.254.50 application/octet-stream 30/Jul/2013:15:12:54 +0530 23079 115.127.17.13 TCP_MISS/200 242118 GET http://r13---sn-cvh7zn7k.c.youtube.com/videoplayback? - TIMEOUT_FIRSTUP_PARENT/10.240.254.50 application/octet-stream 30/Jul/2013:15:12:54 +0530 22254 115.127.19.239 TCP_MISS/200 9663 GET http://r14---sn-cvh7zn7d.c.youtube.com/videoplayback? - TIMEOUT_FIRSTUP_PARENT/10.240.254.50 application/octet-stream 30/Jul/2013:15:12:54 +0530 22283 115.127.17.80 TCP_MISS/200 14214 GET http://r13---sn-cvh7zn76.c.youtube.com/videoplayback? - TIMEOUT_FIRSTUP_PARENT/10.240.254.50 application/octet-stream this same setup was working fine with the squid 3.1 version, all rest of settings are same.... Can this icp_query_timeout directive be broken in recent versions, or can it be related or dependent to some Compilation setting? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/icp-query-timeout-directive-is-not-working-in-3-3-8-for-some-reason-tp4661324.html Sent from the Squid - Users mailing list archive at Nabble.com.
