84647 - PAC: [e-mail]'s file

Status: RESOLVED FIXED

(Core :: Networking, defect)

Description

[Jorrit Tyberghein]

I just downloaded Mozilla 0.9.1 for Windows. At installation time it asked me to 
convert user profile from NetScape 4 which it seems to have done succesfully. 
One of those settings wat the 'automatic proxy configuration' which I need 
here to get past the firewall. However, that doesn't seem to work. Every URL I 
try to open results in:

  The connection was refused when attempting to open ...

In Netscape 4 and in Internet Explorer I'm using the same auto proxy conf 
setting and there it works.

This is a pity because that proxy conf is the only way for me to browse the 
internet.

Comment 1

[Chase Tingley]

Hmm, I'm pretty sure that auto proxy config works now; I wonder if there's a
problem with profile migration of proxies.  

[e-mail]: While I go look for .pac bugs, can you
confirm that your preferences show that the automatic proxy config is set up
correctly?  Edit -> Preferences -> Advanced -> Proxies should have the
"automatic proxy" option selected and show the proxy config url.

Comment 2

[Jorrit Tyberghein]

Yes, I have confirmed that before posting this bug. The setting is correctly 
copied. Even if I manually retype it it still doesn't work.

Comment 3

[benc]

->new

PAC as a feature does load in Mozilla 0.9.1, however there are numerous
implementation features that might be broken.

Please test manual proxy to isolate the problem as relating to PAC, not you
proxy setup.

If manual works fine, then enclose your PAC file so we can figure out which bug
it should be a duplicate of.

Comment 4

[neeti]

-jpm

Comment 5

[Jorrit Tyberghein]

Unfortunatelly I cannot test manual proxy as I don't know the settings and our
sysadmin doesn't tell them. The auto-proxy conf is the ONLY way I can get to
internet :-(

I'm not sure how I can get the .pac file to you? Can I just load it? How?

Comment 6

[benc]

You can capture a pac file via telnet.

I wrote a quick document on it, you can send me feedback directly if it does not
work:

http://frame.packetgram.com/pktg/docs/net/telnetport.html

Comment 7

[Jorrit Tyberghein]

Ok, thanks to your info I was able to see the .pac file. Here it is:

function FindProxyForURL (url, host)
{
	if ((host == "127.0.0.1") || isPlainHostName (host) || dnsDomainIs 
(host, ".uz.kuleuven.ac.be"))
		return "DIRECT";
	else
		return "PROXY www-proxy.uz.kuleuven.ac.be:3128";
}

In this .pac file I also see the direct proxy to use so I tried to fill in 
www-proxy:3128 in the manual settings and it WORKS!!! Of course this means I 
cannot browse locally now so this is not an ideal solution (but better than 
nothing).

Greetings,

Comment 8

[benc]

I'm not seeing any obvious JavaScript problems. Can someone cc a javascript person?

Working w/ manual config:

If you need a working proxy config, you can use manual, and add your domain to
the "no proxy for" field. 

You can also try adding localhost and 127.0.0.1 to the "No proxy for" config,
but there are various reported problems with that.

Analyzing your PAC file:

You can save your pac file locally and use a file:// URL and hack on the file
until it works.

There is also a bug on isPlainHostName (bug 79502).

Comment 9

[benc]

tingley: 
If you have time, can you analyze this bug too? (TIA -Thanks in advance)

Comment 10

[Chase Tingley]

Doing what I can... which isn't that much at the moment.  This is one of the 
simpler pac's I've seen filed.

Comment 11

[Jussi-Pekka Mantere]

Serge, can you take a look at these PAC issues? Thanks - Jussi-Pekka

Comment 12

[basic]

reporter do you see any js script errors in the js console
(Tasks->Tools->"Javascript Console") when you use the PAC?

Comment 13

[basic]

Reporter: This should be working in the latest nightly builds. Please check.

Comment 14

[Chase Tingley]

Cleaning out old PAC reports... this PAC file has no remaining dependencies, so
I'm marking it fixed.  [e-mail], please reopen or
file a new bug if you continue to have problems.