Status

()

Core
Networking
--
major
RESOLVED FIXED
17 years ago
4 years ago

People

(Reporter: a_geek, Assigned: serge (gone))

Tracking

Trunk
x86
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (X11; I; Linux 2.2.17 i686)
BuildID:    2001061000

When I load my proxy autoconfig file, mozilla hangs indefinitely for resolving
www.heise.de which works instantly when I use manual proxy
config. The autoconfig file works fine on Netscape 4.75. Mozilla
displays "resolving www.heise.de" until it returns with a timeout
error. So I guess that it has problems resolving the name to decide
which way to go.

Reproducible: Always
Steps to Reproduce:
1. load autoproxy config
2. try to connect to site, and
3. wait for timeout

The autoproxy script contains an if statement using only the two functions
isInNet() and IsPlainHostName(), and returns either DIRECT
or one proxy specification.


I'm running djbdns' dnscache on this host, and /etc/resolv.conf
contains that as a name server (which is NOT localhost).

I've had similar success with nslookup vs. dig, where dig has
no problems resolving all names fine, but nslookup hangs everytime.

Comment 1

17 years ago
a_geek@web.de, can you attach the PAC file for analysis?  Thanks!
Summary: proxy autoconfig doesn't work → PAC: proxy autoconfig doesn't work

Updated

17 years ago
Blocks: 79893
Status: UNCONFIRMED → NEW
Depends on: 79502, 84798
Ever confirmed: true

Comment 2

17 years ago
-->pac
Assignee: neeti → jpm

Comment 3

17 years ago
Removing the failover dependency as it doesn't actually apply.

From email:

function FindProxyForURL(url, host)
{
  if (isInNet(host, "10.0.0.0", "255.0.0.0")
      || isInNet(host, "192.168.0.0", "255.255.0.0")
      || isInNet(host, "172.16.0.0", "255.240.0.0")
      || isPlainHostName(host) )
    return "DIRECT";
  else
    return "PROXY cache.squid.de:3128";
}
 

> Reasoning: I'm sitting behind a firewall, running my own
> root nameserver for internal names, and also going to an
> external name server for public names. My name server
> makes this transparent to me, so I can as well specify
> internal and external names and get them resolved
> uniformly. This nameserver is mentioned in /etc/resolv.conf,
> and the proxy is (correctly) resolved in this same way
> from the command line and via dig. I have some internal web servers running
> which I can't access using the proxy server, and thus transparently go out to
> the Internet using the proxy if the number resolves to something outside of 
> the private IP space.
No longer depends on: 84798

Updated

17 years ago
Summary: PAC: proxy autoconfig doesn't work → PAC: a_geek@web.de's file

Updated

17 years ago
Depends on: 79057

Updated

17 years ago
QA Contact: benc → pacqa

Comment 4

17 years ago
Serge, can you take a look at these PAC issues? Thanks - Jussi-Pekka
Assignee: jpm → serge

Comment 5

17 years ago
a_geek@web.de: This should be working in the latest nightly builds, could you check?

Comment 6

17 years ago
Cleaning out old PAC reports.  All the dependencies for this bug have been
resolved, so marking FIXED.

a_geek@web.de, please reopen or file a new bug if you've still got issues.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.