Proxy: manual pref requires hostnames not URLs (http://)




19 years ago
3 years ago


(Reporter: prometeo.bugs, Unassigned)




Firefox Tracking Flags

(Not tracked)


(Whiteboard: relnote-user)


(1 attachment)



19 years ago
Using build 2000030313 under Win98.
Prepending the name of the proxy in the configuration with http:// will
stops mozilla from accessing any site.
So: works does not.
Restoring plain name will make mozilla happy again.
It seems to work just fine under linux.

Comment 1

19 years ago
Confirming to put this in better view.
Ever confirmed: true

Comment 2

19 years ago
so if I understand write you are setting your proxy to be http://foo instead of 
just foo? That seems wrong... but I will allow you to help me understand the 
problem correctly.

Comment 3

19 years ago
The behaviour is just like you described. If it's the wrong way to configure the
proxy, then then instructions coming from my ISP are lame. Anyway it worked fine 
under NS 4.x. So maybe this is not a bug, but an idiot-proof enhancement...


19 years ago
Severity: normal → enhancement
Target Milestone: M18


19 years ago
Keywords: beta2

Comment 4

19 years ago
Just an additional note: the mozilla profile manager will not convert the 
http://foo (which works in NS 4.x) in the correct one, so mozilla will be 

Comment 5

19 years ago
Moving beta2 bugs out of M18.
Target Milestone: M18 → M17


19 years ago
Keywords: nsbeta2

Comment 6

19 years ago
Putting on [nsbeta2-] radar. 
Whiteboard: [nsbeta2-]

Comment 7

19 years ago
relnote: remove any leading http:// in proxy configurations in prefs.js
Keywords: nsbeta2 → relnote2
Whiteboard: [nsbeta2-]
Target Milestone: M17 → Future

Comment 8

19 years ago
removing self from cc:

Comment 9

19 years ago
Still very very very broken in Mozilla build 2000080712 (on Linux).  Automatic
proxy doesn't work at all (with or without HTTP).  The result is the same,
Mozilla just doesn't try to access any sites.  Manual proxy works just fine.

Comment 10

19 years ago
An additional comment:  When Mozilla is started with automatic proxy settings
(which don't work), and then is switched to a manual proxy setting, URLs typed
into the address bar still do not work, but all links, bootmarks, and shortcut
buttons do work.

To fix it, you gotta shutdown mozilla. When you come back, Mozilla is happy again.

Comment 11

19 years ago
Some comments on this problem:

* If you have automatic proxy configuration set, then when you try to go
  to a URL in the Location: text field, it calls the section of code in
  .../mozilla/netwerk/base/src/nsProtocolProxyService.cpp about line 255:

        nsCOMPtr<nsIProxyAutoConfig> pac =
            do_CreateInstance(NS_PROXY_AUTO_CONFIG_PROGID, &rv);

This code is failing because the NS_PROXY_AUTO_CONFIG_PROGID component
is not registered.

* The implementation of nsIProxyAutoConfig is done by:
  Yet, from looking at the Makefile in this directory, this JavaScript 
  component is not placed in .../mozilla/dist/bin/components, nor the
  .../mozilla/netwerk/base/public/_xpidlgen/nsIProxyAutoConfig.xpt file.

* If these files are linked into the .../mozilla/dist/bin/components
  directory, and regxpcom run, the code in nsProtocolProxyService.cpp 
  still fails for some unknown reason.

This problem is still under investigation. Suggestions from folks more
familiar with the code (hi gagan! ;-), are very welcome.

Comment 12

19 years ago
Changing the priority of this bug to P2. Getting "file:/" style URL's
working with Automatic Proxy Configuration .pac files is essential to
the internal deployment of Netscape 6 internally here at Sun.
Priority: P3 → P2

Comment 13

19 years ago
Rich: The PAC is a separate problem. In order to get that working see the notes 
at They are not the best notes but 
should allow you to get PAC working. 

Comment 14

19 years ago
Thanks Gagan. So, should we open up a separate new bug for the "file:/" PAC
problem? One of my team is looking at this at the moment, and I wouldn't
be surprised if he doesn't have a fix by the end of the week. 

Comment 15

19 years ago
I don;t have the bug number handy but there is a PAC related bug which basically 
describes the problem of not being able to specify ANY URL for the PAC 
configuration. Currently the only way PAC works is if you copy over the contents 
of that PAC file to the nsProxyAutoConfig.js file. So to answer your question, 
yes feel free to create a new bug but be aware that it would be marked a dup of 
the one I just described (and can't find)

Comment 16

19 years ago
Thanks. I couldn't find it either. I've opened 53080 for the "file:/"
problem, and assigned it to Akhil Arora who is just started looking at it.
Keywords: relnote2 → relnote
Whiteboard: relnote-user

Comment 17

19 years ago
*** Bug 60287 has been marked as a duplicate of this bug. ***

Comment 18

19 years ago
the suggested patch for 53080 fixes this problem. this bug should be closed as 

Comment 19

19 years ago
http bugs to "Networking::HTTP"
Assignee: gagan → darin
Component: Networking → Networking: HTTP
Target Milestone: Future → M19


18 years ago
Target Milestone: --- → Future

Comment 20

18 years ago
Changed summary to say "automatic", so we know we are talking about the same
thing :)
Summary: http:// in proxy configuration breaks proxy → http:// in automatic proxy configuration breaks proxy

Comment 21

18 years ago
gagan (mr. pac-man): sending this your way ;-)
Assignee: darin → gagan

Comment 22

18 years ago
this bug relies on bug 53080 landing.
Depends on: 53080

Comment 23

18 years ago
I have reviewed this bug, and realized that this original problem description
deals with putting a URL rather than a fqdn into the manual proxy fields. (PAC
never worked, so if the reporter says it worked w/ hostnames, it was manual proxy).

I have changed this summary (external-ben corrects internal-ben...), and I'll
look at it soon. All the PAC issues sseem to have their own bug.

My initial feeling is that we should have better documentation first, and add a
friendly error message second (other errors probably are higher priority...)
Summary: http:// in automatic proxy configuration breaks proxy → http:// in manual proxy configuration does not work.

Comment 24

18 years ago
Adding 4xp since this apparently works in 4.x.
Keywords: 4xp

Comment 25

18 years ago
IMO: this should have never worked, because you are pointing to a network
socket, not a URL.

However, I will not mark it invalid since it is a 4xp.

Comment 26

18 years ago
Posted patch patchSplinter Review

Comment 27

18 years ago
Obviously, these fields are supposed to take qdns instead of urls. However, we
have no mechanism for providing feedback to the user, and a 4xp bug in
preferences strikes me as having an implicit profile migration issue as well. 
It seemed easier just to use the educated guesswork of nsStdURLParser to pull
the hostname out of the field rather than trusting the value blindly.  

Please review, especially to make sure I'm not leaking strings.  (I haven't done
much with nsXPIDLCString before.)
Keywords: patch, review

Comment 28

18 years ago
If we had good error checking, then we could error in prefs and when they try to
hit the network w/ a bad pref.

that would solve the migration problem too.

Comment 29

18 years ago

Manual Proxy does not accept URLs

Communicator 4 would accept a URL (http://proxy) in the manual proxy
configuration. Netscape 6 only accepts hostnames. If you migrate a Communicator
4 profile, you will need to change the settings by hand.
Summary: http:// in manual proxy configuration does not work. → Proxy: manaul config does not support URLs (http://)

Comment 30

18 years ago
*** Bug 49018 has been marked as a duplicate of this bug. ***

Comment 31

18 years ago
something to look at again...
Keywords: nsenterprise

Comment 32

18 years ago
-> networking, qa to me.
Component: Networking: HTTP → Networking
QA Contact: tever → benc

Comment 33

18 years ago
marking nsenterprise-; will be reevaluated for nsenterprise in future release.

Keywords: nsenterprise-

Comment 34

17 years ago
gagan: chase has a patch, lets either WONTFIX or change the milestone.

I vote for WONTFIX. I dislike these "4xp was stupid so we need to be also" bugs.

I also went back and confirmed this in Communicator 4, and doing a full URL
parse of manual configs completely confuses the auth dialog, it says things like

The relnote text was really confusing to me, so I sumitted the following correction:

"Communicator 4 allowed URL's in manual configuration, but Mozilla does not. If
you migrate a profile configured this way, you will need to change the URL to a
hostname and port number."
Summary: Proxy: manaul config does not support URLs (http://) → Proxy: manual config does not support URLs (http://)

Comment 35

17 years ago
*** Bug 178337 has been marked as a duplicate of this bug. ***

Comment 36

17 years ago
*** Bug 181152 has been marked as a duplicate of this bug. ***


17 years ago
Summary: Proxy: manual config does not support URLs (http://) → Proxy: manual pref requires hostnames not URLs (http://)

Comment 37

16 years ago
-> defaults.

Darin, can I suggest won't fix for this bug? We have no reports of this problem,
and profile migration of 4xp is not a big deal anymore.
Assignee: gagan → darin
OS: Windows 98 → All
Hardware: PC → All

Comment 38

16 years ago
i don't know... you'd be surprised.  i hear some companies still use 4.x for
internal sites, etc.  and, this is really easy to fix.  i don't mind keeping it
as a future bug.

Comment 39

15 years ago
*** Bug 258378 has been marked as a duplicate of this bug. ***

Comment 40

15 years ago
Actually, I found a message while cleaning out my mailbox, which I can't seem to
find (or maybe I decided they should just comment in the bug if they really
meant it), where they took me to task as an ignorant lout because the original
unix preferences were URLs in the environment variable, and these preferences
were read from the firing shell when navigator was launched from UNIX.


This really should be wontfix for mozilla, and FF can use the new migrator code.

Comment 41

13 years ago
Can I suggest that if this is going to be a WONTFIX, that the direct reference to it in the release notes under Known Issues is removed. I wouldn't have even known about this issue if it wasn't described there.


13 years ago
Assignee: darin → nobody
QA Contact: benc → networking
Target Milestone: Future → ---
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.