Hi, Henrik, It turns out that the bad negative byte hit ratio is due to the iCAP patch I have applied to Squid2.5-STABLE1. After disabling the iCAP module during the configuration and compilation, the byte hit ratio is normal now. However, it is still surprising because I did not enable iCAP in squid.conf when the iCAP module is included, but it gives abnormal byte hit ratio. Any idea about the iCAP patch for Squid? Why it affects Squid in this way?
Regards. Snowy ----- Original Message ----- From: "Snowy" <[EMAIL PROTECTED]> To: "Henrik Nordstrom" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, July 23, 2003 9:23 AM Subject: Re: [squid-users] Range Requests handled in Squid v2.5s1 > Hi, Henrik, > > Got any idea about the Range requests and the negative byte hit ratio below? > > Thanks. > > Snowy > > > > > I just used the default value, which is 0KB. > > > > I have seen a lot of HTTP responses with code=206 in my cache access.log > > file. Amony them, many of URLs refer to the same downloaded file but from > > different clients. I wonder if Squid will count the object sizes many > times > > in this case for server side traffic? Could this cause my cache's byte hit > > ratio negative most of time? > > > > Thanks. > > > > Snowy > > > > > > On Monday 21 July 2003 11.37, Snowy wrote: > > > > Hi, all, > > > > > > > > I am using Squid 2.5.STABLE1 now. I am wondering how range requests > > > > are handled in this version of Squid. How does range_offset_limit > > > > work in squid.conf? > > > > > > What have you set it to? > > > > > > Regards > > > Henrik > > > > > > -- > > > Donations welcome if you consider my Free Squid support helpful. > > > https://www.paypal.com/xclick/business=hno%40squid-cache.org > > > > > > If you need commercial Squid support or cost effective Squid or > > > firewall appliances please refer to MARA Systems AB, Sweden > > > http://www.marasystems.com/, [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > >
