93845 - PAC: bert.laverman's PAC file

Status: VERIFIED FIXED

(Core :: Networking, defect)

Description

[Bert Laverman]

I am behind a firewall/proxy. DNS inside the building will
only work for internal systems. If it try internal servers,
no prob. Any outside system will get me an error popup it
cannot find the site.

We use proxy autoconfig, the function returns a list of
three proxy servers to try for internet access.

Comment 1

[Matthias Versen [:Matti]]

Reporter:
Which build are you using ? (Please include in all your bug reports the build
version).

CC: bbaetz: do you know if this is a dupe ?

Comment 2

[Bradley Baetz (:bbaetz)]

We used to do this, ages ago, but I thought it was fixed. I can't find a bug
(open or closed) about this though.

I'm wondering if this is caused by proxy autoconfig. If you switch to manual
proxy support, does this work?

->gordon, unless it ends up being pac related

Comment 3

[Bert Laverman]

I run Mozilla 0.9.2, build ID 2001062815, on Win-2k.

Yes. If I switch from auto to manual proxy config It will work.
I get the usual id/passwd popup for the proxy.

PS
while using auto on IE or Netscape 4.7-something I get a popup
message first (in the autoconfig code), before it attempts to
connect to te site (through the proxy). Mozilla didn't even give
the popup, it immediately gives the lookup error. "www.mozilla.org
could not be found. Please check the name and try again."

Comment 4

[Bradley Baetz (:bbaetz)]

This is probably a PAC bug - can you connect to external sites by using their IP
address?

Can you attach the pac file?

If you try to connect to www.foo.com through a proxy, and there is an error with
the proxy, error messages refer to www.foo.com - there is an error on that.

Comment 5

[benc]

Bradley,

I think there was a bug about proxy (in general), going to DNS when it
shouldn't. Either that, or it was a comment in one of the massive, marathon bugs..

I am not convinced this is the real problem yet, lets get the PAC file, and then
do another round of analysis.

Comment 6

[Bert Laverman]

Unfortunately, the environment I am in belongs to a bank.
So I'm afraid I can't send you the pac file.

However, I told mozilla to use "file://C|/TEMP/test.pac".
This file contained an alert popup, which it should show
immediately, and returns the usual proxy.
---
function FindProxyForURL(url, host)
{
      alert( "BLAAAARB!\n" );
// Otherwise use local Internet proxy
  return "PROXY tk3p101net.tky.swissbank.com:8080";
}
---
No BLAAARB popup at all.
Same error as before. But then again, it didn't complain when
I gave an invalid filename, so there is a bug there as well.
I don't have an HTTP server at hand to deliver that pac file.
Let me see what I can do without **** off security... ;-)

PS,
this message comes to you using manual proxy config.
_That_ works.

Comment 7

[Bradley Baetz (:bbaetz)]

alerts won't display, because of the way we're sandboxed. That is unlikely to
ever be fixed, although theres a bug on it somewhere.

What if you change the domainname to an IP address in the pac file? what if you
try to connect to http://207.200.81.215/ (which is www.mozilla.org), with and
without making that change?

Comment 8

[Bert Laverman]

A nice long wait followed by "The connection was
refused when attemptin to contact 207.200.81.215."
Changing the proxy server's name into its IP address
doesn't help either.

Comment 9

[Bradley Baetz (:bbaetz)]

Can you try a pac file which just has a single line in the function, returning
the proxy?

Also, try removing the alert line. That should make it work. If it doesn't, is
there anything in the javascript console?

I just noticed that you were using 0.9.2. Try 0.9.3 - I'm wondering if you're
running into bug 80363 - you'd get the same problem if your host didn't have a
reverse address.

Comment 10

[Bert Laverman]

Replaced 0.9.2 with 0.9.3 (still on Win2k):
    No change
1-liner functione:
    No change
Javascript console showed error on alert call,
no new errors since then.
Are you suggesting that an alert() call (which works for IE
and netscape) prevented it from getting to the return?
Anyways, it still won't work.

Comment 11

[Bradley Baetz (:bbaetz)]

I was considering the alert being a problem, but if removing it didn't help...
I'll have to think about this a bit.

Comment 12

[benc]

Administravia for PAC:

+cc tingley, the de facto leader of all things PAC.

Alerts are broken in bug 86846.
Error for failed load is 90308.
Marked as depednencies + registered this bug w/ the meta bug as a blocker.

bbaetz: did the reverse lookup bug affect NT as well? Also, we skipped a step,
we need to verify file URL's work on NT, the original checkin was targed for
Solaris. I don't think other people are using file URLs in any bugs I have seen.

bert: A PAC file can live on any kind of web server, its just a file. Can you
move it to any server, even a Mac running that personal web sharing service...

re: DNS: the status lines and errors for proxy are all wrong, unless you have a
DNS server log, lets assume this is a PAC connectivity problem.

Comment 13

[Bradley Baetz (:bbaetz)]

benc: I was going to test this yesterday, but I wasn't able to log in all day.
Hopefully I can fdo this today.

Comment 14

[Matthias Versen [:Matti]]

Bradley: Any progress ? (Can we mark this bug NEW ? )

Comment 15

[benc]

matti:
It might make the mozilla.org world more confusing, (I hope not), but as far as
networking bugs go, I'm encouraging people to do what they think is right. I'd
like to encourage people to act first, as long as you leave a brief comment
explaining why. I try to do the same, so my actions make sense to you.

For example, in the case of PAC, if it looks like their file is affected by any
PAC problem, it's basically confirmed. So you can move this to "NEW"...

Comment 16

[Matthias Versen [:Matti]]

marking NEW
Benjamin: Thanks for your comment. I'm now very careful with some bug changes 
because i got some negative comments from a few developers/QAs.
I thought a few days that I should better stop my Mozilla Project help...

Comment 17

[Darin Fisher]

reporter: could you please verify this bug using a recent nightly build?  thx!

Comment 18

[Bert Laverman]

Yes! Apart from the fact that the error on the alert()
seems not to allow Mozilla to continue with its work
(naughty!), if I remove the alert it _will_ work.

So, whatever it was you did for build nr 2001100903, it
almost made Mozilla work. :-) Now let it treat the alert
as something to complain about but still continue, and
I'm a happy puppy.

Comment 19

[gordon]

Marking FIXED as per reporter's comment.

Comment 20

[benc]

VERIFIED/fixed: (fixing the PAC file makes the bug INVALID..., Darin has fixed
the Mozilla bug for 1.6b!)