Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!news.bri.connect.com.au!fjholden.OntheNet.com.au!not-for-mail From: Tony Griffiths <tonyg@OntheNet.com.au> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Weird Apache/Routing Problem. Date: Wed, 16 Apr 1997 11:32:23 +1000 Organization: On the Net (ISP on the Gold Coast, Australia) Lines: 35 Message-ID: <33542C27.3D8C@OntheNet.com.au> References: <334DEBED.167EB0E7@silas.cc.monash.edu.au> <zUEJ$MD4F99anz6@rb.xs.use.ch> <3350CF92.41C67EA6@silas.cc.monash.edu.au> Reply-To: tonyg@OntheNet.com.au NNTP-Posting-Host: swanee.nt.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (WinNT; I) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:39123 > > > If I specify the URL as http://127.0.0.1/ my ISP's machines send back an > > > error informing me that the connection failed. I'm not surprised... Where exactly is the proxy going to go for that IP address? Itself! But it's a proxy, NOT a Web server... > But I've set the proxy settings in Netscape so I don't use proxies > for my localhost (i.e. the *.dinosaur.com.au domain) and my ISP. It > should be noted that dinosaur.com.au is not a registered domain name. > Simply one I'm using on my local machine so I can learn about DNS etc. > > My routing table looks to be correct and I can ping and traceroute all > hosts configured in my DNS setup. > > Turning proxies off clears up the problem, but is not the solution I'm > looking for. I obviously need to specify multiple domains in Netscape's > proxy setup that I do not wish to use proxies for. > > Your help much appreciated. Be aware that the "no proxy" stuff of Netscape is CASE SENSITIVE whereas DNS is as a whole is not! Eg. onthenet.com.au != OntheNet.com.au !!! I have specified multiple domains and hosts as a comma separated list and, apart from the above problem, it seem to work. If you are operating from a "rogue" domain, then it is possible that the proxy is getting upset because it will be trying to back-translate your IP addresses into host.domain strings which might be used for authentication. Eg. We restrict access to our proxy to our customers. I can only suggest that you get 'your' domain officially registered and delegated! Tony