Try looking at max_reply_body size and max_reply_header on your backend...some websites are braindead and send the whole thing back as a header, instead of sending a header and a body. I bet you are hitting the limit on that, since that affects ALL things, not just cached items. On Thursday 31 March 2005 10:14 am, Marco Crucianelli wrote: > I've just started implementing my squid "solution" after a long studying > period...right now I've got this problem: I've got a frontend squid > working like a Layer7 Switch for a backend squid, configured like parent > proxy using: > > cache_peer 10.50.5.80 parent 8080 3130 proxy-only > > > in the frontend squid.conf > Now, I wanted to use the front end squid for small files only (thus I've > used max_obj_size 4096KB) while the backend squid for big files (using > max_obj_size 2000000KB). Now the problem is, whenever I try to download > a big file, therefore passing through the frontend squid, I only get 4MB > of that file. It seems like the frontend squid "cut" the connection with > the backend squid while this one is sending back the file! Why?!? I > mean: reading the squid.conf.default "max_object_size file_size" should > only tell squid not to cache anything bigger than file_size, while, in > my case, it seems like it even makes it stop receiving the file!!!?? > Maybe it's my fault? Couldn't I understand how it really works or what? > > Thanks in advance > > Marco Crucianelli
