On Fri, 2005-04-01 at 11:22 +0200, Henrik Nordstrom wrote: > On Fri, 1 Apr 2005, Marco Crucianelli wrote: > > > Well, I've just checked and, as I thought, reply_body_max_size is not > > set in both frontend and backend squid. I mean, the line is commented in > > both squid.conf > > What seems to be even more weird is that I've been doing more trsting > > yesterday and it seems like max_obj_size is the real problem. I've tried > > setting it to 40MB for example on the frontend squid, thus I could get > > file up to 40MB from the backend! > > Which exact version of Squid is running on the frontend (including > patches)? > This is what I get when I've tried downloading a 60MB file (thus using backend squid via frontend squid) that stopped at 38MB, reading the access.log from the frontend squid: 1112346267.495 58197 10.50.5.166 TCP_MISS/200 11373047 GET http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/releases/x86/2005.0/installcd/install-x86-universal-2005.0.iso - TIMEOUT_FIRST_UP_PARENT/10.50.5.80 text/plain Is there anything dealing with cache_peer_timeout that I can do, or it will be useless?!!? Thanks! Marco
