From owner-freebsd-net Fri Jan 7 19:34:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from netcom.com (netcom10.netcom.com [199.183.9.110]) by hub.freebsd.org (Postfix) with ESMTP id BAD0E14E22 for ; Fri, 7 Jan 2000 19:34:21 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id TAA07445 for freebsd-net@FreeBSD.ORG; Fri, 7 Jan 2000 19:34:20 -0800 (PST) From: Stan Brown Message-Id: <200001080334.TAA07445@netcom.com> Subject: Help please with proxying for Netscape. To: freebsd-net@FreeBSD.ORG (FreeBSD Networking) Date: Fri, 7 Jan 2000 22:34:20 -0500 (EST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry to post this here, but I sent it questiosn, where it was met with a resounding silence. I really need to understand this. I have several FreeBSD machines which live behind a coporate firewall. Untill recently access to http browsing was on "need only" basis. It was throught a SOCKS firewall that did some sort of authentication. Now it has been opened up to "everyon", except the MIS types on "support' microsloth machines :-( After having looked at one of thes machines, I see that Nescape on the is configured to use "automatic proxyin" and this proxy is pointed to a file on a Novell fileserver. Here are the contents of this file: function FindProxyForURL(url, host) { if (isInNet(host, "170.85.18.11", "255.255.255.128")) return "SOCKS 170.85.17.10:1080; DIRECT"; else if (isInNet(host, "170.85.0.0", "255.255.0.0")) return "DIRECT"; else return "SOCKS 170.85.17.10:1080; DIRECT"; } Now, what this does is pretty obvious, if the reference is outside our corporate net (170.85.*) it calls a SOCKS proxy, otherwise, it goes direct. I need to be able to replicate this behavior for the UNIX machines behind the firewall. I have a internal FreeBSD machine that runs Apache, that I think I can do this with, but just putting this file on it, and pointing my UNIX clients to it results in nescape error, referencing a MIME type error. Can someone please educate me on how to make this work? Thanks -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message