Every iteration of stable release has some fixes for known problems, and might also inadvertently introduce a new problem, which has to be fixed after a bug report is done. That is why it is suggested to use the latest version, so that the developers can work on the latest code. As you can understand, the latest code has the most developers involved. Another test that you could do, is to copy the file to some http server that you control, and then try to access that file through the proxy. Even if you do encounter a problem in this setup, you'll still have to try with the latest version. Regards HASSAN On Thu, May 13, 2010 at 01:59, Emmanuel Lesouef <e.lesouef@xxxxxxx> wrote: > > Le Wed, 12 May 2010 08:38:31 -0800, > James Zuelow <James_Zuelow@xxxxxxxxxxxxxxx> a écrit : > > > Backports has 2.7STABLE7 which is newer than the Lenny version, if > > not quite up to date. 2.7STABLE9 has been in Squeeze for a couple of > > weeks (since April 28) so might be in the backports pipe now. > > > > That might be a simpler upgrade path. (Assuming that the Lenny > > version of squid is your problem.) > > > > I agree, this is a simpler path to upgrade as backports are already > activated on this server. > > But the main question remains : is the version of squid the problem ? > > I will test the backport version later. > > Sounds strange to me that no one using Debian Lenny with squid stable > didn't encounter the problem... > > Thanks for your answers, btw. > > -- > Emmanuel Lesouef > > >
