Use Transparent Proxy or Non-Transparent Proxy?

Just to clarify.  My understanding of a transparent proxy is that your local border firewall - let's says 192.168.1.1 - port forwards http (80), https (443), ftp (21/22) and sometime SOCKS traffic towards a dedicated WEBserver, lets say 192.168.1.2.  Like WEBSense, TitanHQ, Bluecoat, Spywall, or others.

Some answers here suggest firewalls scanning directly http (80), https (443), and ftp (21/22) traffic is a transparent proxy.  In others words, as long as there is no setup on users' WEB browsers, (PAC file, GPO, ET.c.) - dedicated WEB filtering appliance or not - it is considered transparent proxy.

That said. what I do not like with non-transparent proxy, is that the firewall reports all WEB traffic as being done by the WEB appliance admin user.  Forcing manager to navigate both firewalls and WEB appliance logs, trying to make sens out of it.  Colossal waste of time.  Also, non transparent is somewhat unreliable, and requires tons of setups.  Pac files, GPO, scripts, name it.

Just to clarify.  My understanding of a transparent proxy is that your local border firewall - let's says 192.168.1.1 - port forwards http (80), https (443), ftp (21/22) and sometime SOCKS traffic towards a dedicated WEBserver, lets say 192.168.1.2.  Like WEBSense, TitanHQ, Bluecoat, Spywall, or others.

Some answers here suggest firewalls scanning directly http (80), https (443), and ftp (21/22) traffic is a transparent proxy.  In others words, as long as there is no setup on users' WEB browsers, (PAC file, GPO, ET.c.) - dedicated WEB filtering appliance or not - it is considered transparent proxy.

That said. what I do not like with non-transparent proxy, is that the firewall reports all WEB traffic as being done by the WEB appliance admin user.  Forcing manager to navigate both firewalls and WEB appliance logs, trying to make sens out of it.  Colossal waste of time.  Also, non transparent is somewhat unreliable, and requires tons of setups.  Pac files, GPO, scripts, name it.