Bon, pour ceux qui ne veulent ni lire, ni
réfléchir un peu : (cf FAQ de Squid
http://wiki.squid-cache.org/SquidFaq/In ... d401533ac7 )
Why can't I use authentication together with interception proxying?
Interception Proxying works by having an active agent (the proxy) where there should be none. The browser is not expecting it to be there, and it's for all effects and purposes being cheated or, at best, confused. As an user of that browser, I would require it not to give away any credentials to an unexpected party, wouldn't you agree? Especially so when the user-agent can do so without notifying the user, like Microsoft browsers can do when the proxy offers any of the Microsoft-designed authentication schemes such as NTLM (see ../ProxyAuthentication and NegotiateAuthentication).
In other words, it's not a squid bug, but a browser security feature.
C'est clair cette fois ci ?
NB : personnellement j'utilise pfSense (dans plusieurs entreprises) : il utilise, comme Ipcop, les mêmes recettes : Squid, SquidGuard ...