Please, consider the network topology below. I could always configure outgoing http traffic on the firewall to authenticate with firewall user. How is this different from having squid authenticate in transparent mode? WAN || || wccp/gre tunnel || squid==============================Fortigate FW/RT Int ip 1 192.168.8.1 3.3 || Int ip 2 192.168.11.1 ip: 192.168.8.21 || Ext ip XX.XX.XXX.24 || || WLAN Router Int. ip 192.168.11.32 Ext. ip 192.168.7.1 || || || Client Workstation 192.168.7.110 On Wed, Feb 20, 2013 at 7:55 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On 21/02/2013 4:42 a.m., Roman Gelfand wrote: >> >> I guess the 2 don't mix as per "NOTICE: Authentication not applicable >> on intercepted requests." message. >> >> Would it follow user access control via transparent proxy? or is there >> a way around the above limitation? > > > Please read the Interception Proxy FAQs: > http://wiki.squid-cache.org/SquidFaq/InterceptionProxy#Why_can.27t_I_use_authentication_together_with_interception_proxying.3F > > Amos