Name: mt13159 Date: 07/27/2000


Both the 1.1.3 and 1.3 plugin do not read proxies from Netscape 4.5 and later correctly.
In 1.1.3, the problem is that it is not locating the Netscape prefs.js file correctly. It attempts to find this file by using the Netscape biff "popstatePath" Windows registry key. This key won't exist if the user has an IMAP server configured instead of a pop server. When this fails, it then tries to look for the file in a default location. This default is obtained by taking the Netscape "Install Directory" registry key and appending "Users" to it. However, the Users directory is actually one level above Install Directory, so this fails, too. Further, when creating a profile the user can put it in any directory they want, so assuming it is in this location is incorrect. The end result is that no proxies are used for plugin 1.1.3 when the user has an IMAP server configured for email.
In plugin 1.3, it seems to always use the Internet Explorer proxies, even when using Netscape. I haven't looked into exactly why this is happening.
The root of the problem is that, in Netscape 4.5, Netscape moved all their registry keys out of the Windows Registry and into their own Netscape Registry. The correct way to obtain the prefs.js file for the current user is to use the new Netscape Registry keys. These are stored in a file called nsreg.dat. You will need to write a parser for this file, but since the Mozilla source code is public, this is easy to do. I can give you some samples, or just go to http://www.mozilla.org/ for an example of how to do this. See the file reg.c.
The keys you should be using in the Netscape registry are:
Common\Netscape\ProfileManager\LastNetscapeUser
  Users\<username>\ProfileLocation
These two keys will give you the correct location of the prefs.js file. You can then read the proxies from that file.
(Review ID: 107645)
======================================================================