Closed
Bug 49297
Opened 24 years ago
Closed 24 years ago
Proxy Auto Configuration does not work
Categories
(Core :: Networking, defect, P3)
Core
Networking
Tracking
()
Future
People
(Reporter: chris.beere, Assigned: gagan)
References
Details
Attachments
(2 files)
M17 build, Windows NT 4.0 service pack 5. Bug 20145 not fixed in M17. If i set
the config. to "direct to the internet" the browser tries to resolve the URL I
entered. It fails as I have no direct connection to the internet now. When I set
the auto configuration with the details of my Netscape 4.7 browser nothing
happens.
I suspect 20145 is not fully fixed,
regards
Chris Beere
Comment 1•24 years ago
|
||
I don't think your report is particularly clear my first impression was you were
expecting proxy autoconfig to work when you had it set to direct connection to
the internet which of course it won't. After a closer look I'd say you tried the
following (correct me if I'm wrong):
1. Set proxy settings to direct connection - noticed that Mozilla tries to
connect (throbber moving, etc)
2. Set proxy settings to auto config using the auto config URL as used by
Netscape 4.x. Try to visit a site and no activity occurs in the browser whatsoever.
I've actually just tried setting a proxy using auto config and I get absolutely
no response from the browser. I'll attach the .pac file for your enjoyment and
I'll confirm this bug.
This is also Windows NT (no idea what service pack) using build 2000081508.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•24 years ago
|
||
Comment 3•24 years ago
|
||
A strange side effect of this bug is that it also stops the mail folders
appearing if you have your proxy auto config on and then start mail. You get a
mail window with all three panes blank.
If you then switch the setting back to direct connection you can thn close mail
and reopen it successfully with all the folders in place.
It might be worth spinning this mail problem off as a separate bug but I'll
leave that to whoever it gets assigned to.
I've also reproduced the bug on a recent Mac build so changing OS/platform to All
OS: Windows NT → All
Hardware: PC → All
Comment 7•24 years ago
|
||
Any new info on this one? Were getting a lot of new incoming bugs mentioning it.
Comment 8•24 years ago
|
||
Comment 9•24 years ago
|
||
This is a note for my attachment 10 [details]/15/00 18:02.
The attached file is our corporate auto-config file that does not work with M18.
A URL pww.philips.com should not go through the proxy, whereas www.philips.com
should go through the proxy. A URL pww.lighting.philips.com should not through
the proxy, but www.lighting.philips.com should go through the proxy.
With M18, using the autoconfig file attached, the browser seems to hang after
reload; it will not visit new URLs. (the autoconfig URL is
http://pixs00.peap.psg.philips.com:8081/pixs.pac )
Comment 10•24 years ago
|
||
Above commentary means that I don't know how to manually configure the proxy to
work properly, because telling the proxy to ignore '.philips.com' won't work for
the 'www.*.philips.com' sites, which need to go through the proxy. If this
auto-config bug is not fixed, I can't use M18 on our corporate intranet. If
someone can give me a setting to use the manual proxy config, much appreciated,
otherwise, I suggest this become a P2 or P1 bug.
Comment 11•24 years ago
|
||
Same as bug 53080, I think.
Comment 12•24 years ago
|
||
Hi.
I have Mozilla M18 ID Build 2000091312 in win95.
Today in my university arrange a Proxy server using Squid 2.3 Stable 4.0 in
linux mandrake 6.1. For this configuration i need a change my
browser preferences in advanced proxies -> automatic proxy configuration:
proxy.upb.edu.co/config.pac.
After that, my mozilla don´t working. For this reason this report I need use a
Nestcape 4.6 with this configuration in proxy.
For me this problem is CRITICAL.
Thanks for helping.
Excuse me for my few english.
Comment 13•24 years ago
|
||
*** This bug has been marked as a duplicate of 53080 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•