Web-Based Proxies As Internet Gateways? 5
"I attempted to get around this problem using the freely downloadable PERL based CGIProxy 1.3 through NAT, bypassing the Novell proxy but still using the firewall aspect. It's a wonderful script but in its current downloadable form, it doesn't support SSL or Javascript, both of which we need.
My ideal solution is a product like CGIProxy since it would allow pretty much transparent access to the designated sites via links from our Intranet. I have done some more research but have run out of ideas and time and was hoping the Slashdot community could throw some ideas my way.
NT or Freenix solutions are acceptable. I have some coding ability but I am pretty far away from considering myself a programmer so solutions that require a decent amount of recoding probably won't work for me.
Thanks in advance for your help."
how about RADIUS? (Score:1)
Apache (Score:1)
http://www.apache.org/
Runs under NT, and many *nix's.
It's not just for webserving anymore.
Bordermanager (Score:1)
Try NT Proxy (Score:2)
Squid works well for me (Score:1)
All internal traffic on port 80 is redirected through Squid (on port 3128) via ipchains, and Squid can then use its redirector to filter and/or redirect URLS. - in my case the redirector is a simple perl script that simply uses regular expressions to match and replace URLS.
You also get caching with squid, of course.
So you could use it to filter anything that didn't match the appropriate pattern and redirect that request to a 'sorry you can't access that site' page on your intranet.
It also lets users behind the NAT gateway use the same URLs to access web servers as they would outside the firewall.
Squid also has authentication features i believe, but i'm not familiar with them.
Client setup in completely transparent, the browser doesn't even know its talking to a proxy server.
I couldn't be happier, since it means that MS Proxy Server 2 is going on its long-awaited trip out the window.