Steffan Davies wrote: > It's been awhile since I last played with transparent proxying, but IIRC > the proxy itself doesn't have to know that it's being given intercepted > traffic rather than being connected to directly by clients and the > router configuration needed to set up the redirection of 80 and 443 to > the proxy is only a couple of lines.
That's not my impression last time I looked at transparent proxying. The guides for setting up transparent proxies I have seen involve using SQUID in a reverse proxy mode, and then using say iptables to redirect the traffic from 80 to our proxy port. Besides, this is all moot, as you can't transparent proxy HTTPS. Once again, school's use cache appliances supported by a particular vendor. If their product doesn't support transparent proxying, then it doesn't support transparent proxying. > This being the case it's probably > easier to fix your network configs than every application a user might > wish to run. I wouldn't call it "fixing" our config, I'd call it fixing someone elses's mistake, because application writers, who have large audiences using proxy servers, can't be bothered, or are too inept to support them. We have software suppliers who are specifically Education software suppliers who don't seem to get their heads around the idea that school's run proxy servers. > That said, the lack of configuration available to Kontiki users is a > pain in the neck. I know several people who've uninstalled it because > its non-adjustable upload was crippling their asymmetric cable/ADSL > connections by delaying ACKs. Wow, the upload is still non-adjustable? Poor. Graham. - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/[email protected]/
