You have two problems. The first one is that you are using a broken
version of Netscape which has problems handling the "Security proxy"
settings. The workaround to that part of the problem is to write the
proxy name differently than the other proxies (for example all
uppercase, and the other all lowercase).
Second is the "No route to host" error. Possible explanations is if
support.sybase.com is down, or you have a firewall which probit squid
from directly accessing port 443 on that host. Port 443 is the SSL port
used for https connections.
If your Squid is inside a firewall then you either needs to open up
access to port 443, or use the never_direct option in squid.conf
depending on your firwall type and setup.
-- Henrik Nordstrom Spare time Squid hacker Joel Taqueban wrote: > > > I can't seem to access the site below, what's wrong? I'm using > Squid/2.2 Stable 3. I always get a URL error. What does the port > '443' in > support.sybase.com:443 mean? The below url has a reference: > > http://sdn.sybase.com/sdn/appdev/appdev_home.stm > > Awaiting kind reply? > > Joel > > https://support.sybase.com/cust_prim/cgi-bin/Logon.cgi?refer=http://sdn.sybase.com/sdn/appdev/get_doc.stm?loc=1001498 > The system returned: > > (113) No route to hostReceived on Fri Aug 06 1999 - 03:50:38 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:47:52 MST