i have couple of things things:
i have made a long way of testing squid for a couple of days on various versions of linux distors such as centos 5.7\6.0\6.2 fedora 15\16 ubuntu 10.04.3\11.10 gentoo(on the last portage) using tproxy and forward proxy. (all i686 but ubuntu x64) i couldnt find any solid info on squid to work with these systems so i researched.
i have used squid 3.1.18 3.2.0.8 3.2.0.13(latest daily source) 3.2.0.14.
on centos and ubuntu squid 3.2.0.14 was unable to work smoothly on interception mode but on regular forward mode it was fine.

on the centos 5 branch there is no tproxy support built-in the regular kernel so you must recompile the kernel to have tproxy support. on the centos 6 branch there is tproxy support built-in the basic kernel but nothing i did (disabling selinux, loading modules and some other stuff) didnt make the tproxy to work. because i started with centos i throughout that i'm doing something wrong but after checking ubuntu, fedora and gentoo i understood that the problem is with centos 6 tproxy or other things but not squid.

also i didn't found any logic README or info about tproxy that can explain the logic of it so in a case of problem it can be debugged.

after all this, what do you think about releasing a list of "supported" linux distors that seems to work fine on every squid release?
i'm talking about the major releases and not about "puppy linux" or "dsl".

this is the place to rate the linux distro you would like squid to be tested on.


another subject:
what dynamic content or uncacheable sites by squid will you want to to be able to cache?

let say youtube. ms updates and stuff like that.
i know that cachevideo is available but i think that with some effort we can build some basic concept that will benefit all of us.

votes for sites will be gladly accepted.

(i will be glad to explain the reasons that makes these sites objects uncacheble in many cases to anyone that want to understand it.
also how and why squid is doing such a great job.)


Regards
Eliezer





Reply via email to