> -----Original Message----- > From: Henrique Machado [mailto:henrique.cicuto@xxxxxxxxx] > Sent: Tuesday, 03 February, 2009 10:26 > > 1233662651.716 0 192.168.1.74 TCP_DENIED/407 2451 GET > http://security.debian.org/dists/etch/updates/main/source/Sour > ces.diff/Index > - NONE/- text/html > 1233662651.761 0 192.168.1.74 TCP_DENIED/407 2463 GET > http://security.debian.org/dists/etch/updates/contrib/source/S > ources.diff/Index > - NONE/- text/html > > As you can see, only 407 answers. > Do you see how there is a dash between "Index" and "NONE"? That is where the username would be. So the apt process is not passing a username to squid. (Which explains why it can't authenticate!) It isn't a typo in the password. If I change the password in my /etc/apt/apt.conf, I get 407 denied errors, but the username is still logged. It is as if your apt installation is not reading the /etc/apt/apt.conf file. > Here's my apt.conf: > > Acquire::http::Proxy "http://me:123456@<squidbox_IP>:3128/"; > > And that's it. I've got no clues at all. This looks correct. As long as the path and permissions are correct, apt should be reading it. Anyway, I think you are having a problem with apt, not with squid. Please reply off list and we'll see if we can't work it out. If it turns out to be squid after all we can post the solution back to this list. Cheers, James
