20680 - Unable to use Proxies for firewall

Status: CLOSED INVALID

(Core :: Networking, defect, P3)

Description

[Theo Jakobus]

I started with M10 on my PWS 500au under OpenVMS V7.2-1 setting the
proxies for our firewall. I was able to connect to outside URLs.
I did now the first steps with M11 but I can't pass the firewall.
I checked the file [._MOZILLA.MOZPROFILE]PREFS.JS there are
the entries:
user_pref("network.proxy.type", 1);
user_pref("network.proxy.http", "iaf.iaf.fhg.de");
user_pref("network.proxy.http_port", 81);
user_pref("network.proxy.ftp", "iaf.iaf.fhg.de");
user_pref("network.proxy.ftp_port", 81);

Is this a bug or did I something wrong?

Starting Mozilla I always get the message:
$ @sys$common:[mozilla]mozilla
Starting mozilla-bin...
module->RegisterSelf failed(80510008)
module->RegisterSelf failed(80510008)

Comment 1

[Chris McAfee]

I don't understand why this is an architecture bug.  Moving over to Browser.

Comment 2

[Chris McAfee]

I thought proxies were working, over to gagan.

Comment 3

[Warren Harris]

Mass move of all bugs without target milestones to M13.

Comment 4

[Colin Blake]

I think this is an OpenVMS-specific problem. I'll take it.

Comment 5

[Colin Blake]

Theo, first thing is to figure out what isn't loading (the cause of the
module->RegisterSelf failed(80510008) messages). Can you edit MOZILLA.COM,
and comment IN the line which defines VMS_TRACE_FILENAMES.

Start MOZILLA. You'll get a lot of output. What I need to see are the lines
just before the "module->RegisterSelf failed" messages. Can you post them
here (not all the log, just a few lines). Thanks.

Comment 6

[Colin Blake]

Theo, thanks for the mail containing the log info (next time please
post your reply into the Bugzilla system so that the information
doesn't get lost). Unfortunately that information didn't reveal
very much and I still don't know what's causing the messages.

You say that you had M10 installed and working. Did you delete all your profile
tree before trying M11 (this is documented in the release notes). I ran in to
problems myself with the M11 code, and these went away when I deleted my profile
and started Mozilla again (after Mozilla creates a new profile you will need to
exit Mozilla to define your proxy information again). Please try this and let
me know what happens.

> I get a lot of errors "failed to find ..." like:
> dlsym_Jacket: failed to find NSGetModule in libwidget_gtk.so

These are normal. There are two possible interfaces that a component can have
(NSGetModule and NSGetFactory), and Mozilla tries both. This is just the first
interface failing. So long as there is a matching GetFactory that doesn't fail,
all is well.

> I have no experience with JAVA.

There is no Java support in Mozilla at the moment, and it looks like it won't
be there for a while. Mozilla requires OJI which is present in JDK 1.3, and
it looks like it will be quite a while before this is available for OpenVMS.

Please reply back here once you've tried with a clean profile.

Comment 7

[leger]

Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.

Comment 8

[Colin Blake]

Theo, any news on this one?

Comment 9

[Colin Blake]

From Theo:

I deleted the tree starting with _MOZILLA in my SYS$LOGIN, then I
started
MOZILLA, created a new user profile, and added the information for the
proxies.
There is now a subdirectory tree starting with _MOZILLA in my SYS$LOGIN.
Starting MOZILLA again and pushing the M button gives:
$ @sys$common:[mozilla]mozilla
Starting mozilla-bin...
module->RegisterSelf failed(80510008)
module->RegisterSelf failed(80510008)
Successfully created instance of session history
Setting content window
browser.startup.page = 1
startpage = www.mozilla.org
Document about:blank loaded successfully
Document: Done (0.279 secs)
got observer service
added observer
Error: Can't load: http://www.mozilla.org/ (804b000e)
failed to set the page title.
Error loading URL http://www.mozilla.org/
Document: Done (36.152 secs)
$

Comment 10

[Colin Blake]

I'm really at a loss on this one. Here's a couple of things to try, but I
wouldn't bet a lot of money on either doing much good:

1. Mail me the output of the following:

   $ show work
   $ mcr sysgen show wsmax

   Its possible this problem is quota related.

2. Delete the file COMPONENT.REG from the root Mozilla directory. Run Mozilla
   again. It will automatically re-register all the components (may take a
   minute or two, don't give up on it!) and re-create COMPONENT.REG.

   Maybe something in the component registry got corrupted.

If neither of these help, then perhaps the next baselevel, M12, will work for
you. M12 is in final testing and should hopefully be released in about a week.

Comment 11

[Colin Blake]

[responding to private mail from Theo]

Great. So recreating the component registry fixed the RegisterSelf problem.
One down and one to go. On to the firewall problem.

You say that your firewall server was updated at the same time when you
installed M11 and Mozilla stopped working. This is indeed very suspicious.
Here's a test you can do to determine if your firewall is correctly
configured. We will use telnet to talk directly to the proxy server on
firewall, and fetch a web page manually. If this works, then problem is
in Mozilla. If this doesn't work, then the problem is in your firewall
configuration.

Please follow these directions precisely. Once you are connected via telnet
to the firewall, you have to type in a GET command. You MUST NOT make any
mistakes when typing this line in as you CAN NOT use the DELETE key (I
usually cut/paste the line to avoid any typos). You will also be typing
this GET line OVER THE TOP of existing output - this is normal.

<RETURN> just means hit the RETURN or ENTER key.

This test assumes that your proxy server is iaf.iaf.fhg.de and proxy port
is 81 (based on information you entered into the bug report).

$ telnet iaf.iaf.fhg.de 81<RETURN>
GET http://www.mozilla.org HTTP/1.0<RETURN>
<RETURN>

The HTML from the main Mozilla web page should now be displayed.

Did it work????

Comment 12

[Colin Blake]

Theo just sent me mail. The telnet test failed. It came back with

HTTP/1.0 408 Request Time-out

He's off to talk to his network staff now as this is a local network issue, not
a Mozilla bug.

Comment 13

[Colin Blake]

This is resolved. Customer is happy. I'm closing.

Comment 14

[David Krause]

Fixing qa contact.