URI called twice & NTLM problems when starting Prism webapp using a registered protocol handler

UNCONFIRMED
Unassigned

Status

Mozilla Labs
Prism
--
major
UNCONFIRMED
8 years ago
7 years ago

People

(Reporter: mario.rasch, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729; .NET4.0E)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2pre) Gecko/20100322 Prism/1.0b4

I've set up a webapp that launches the URI "http://localhost/webapp.htm" (this is the URI configured in webapp.ini).

"webapp.htm" registers a protocol handler using "window.platform.registerProtocolHandler("phone", "http://localhost/webapp.htm?n=%s".

Registering this protocol handler leads to a corresponding registry entry "...\HKEY_CLASSES_ROOT\phone" that uses the command line '"C:\Programme\prism\prism.exe" -override "C:\Dokumente und Einstellungen\user\Anwendungsdaten\WebApps\webapp.test@prism.app\override.ini" -webapp "webapp.test@prism.app" -url "%1"'.

I encountered some problems as described below:

1. Clicking a link like '<a href="phone:%2b49%2012345678">+49 12345678</a>' in Internet Explorer correctly opens my webapp with Prism, *BUT* my webserver protocol proves that the URI "http://localhost/webapp.htm" gets called twice!

2. Change the parameter "-url" in the above mentioned command line in the registry to "-uri".

3. Then, when clicking a link like '<a href="phone:%2b49%2012345678">+49 12345678</a>' in Internet Explorer, the URI "http://localhost/webapp.htm" correctly only gets called once, *BUT* an additional dialog gets displayed (title: "Launch Application", text: "This link needs to be opened with an application. Send to:"). Just closing this dialog does not seem to have any negative effect.

4. Change the parameter "-uri" in the above mentioned command line in the registry back to "-url".

5. Configure "localhost" to only allow NTLM authentication.

6. Then, clicking a link like '<a href="phone:%2b49%2012345678">+49 12345678</a>' in Internet Explorer correctly opens my webapp with Prism and a dialog is displayed that lets me enter my NTLM credentials, *BUT* after that, nothing more happens, i.e. the webapp main window remains white and the URI "http://localhost/webapp.htm" is not displayed.

7. Change the parameter "-url" in the above mentioned command line in the registry to "-uri" again.

8. Repeating the steps in point 6 correctly launches my webapp in Prism and displays the URI "http://localhost/webapp.htm" after I entered my credentials, *BUT* the same "Launch Application" dialog is displayed as described in point 3.

Reproducible: Always

Steps to Reproduce:
See details.


Expected Results:  
1. The configured URI should not be called twice when starting a webapp using a registered protocol handler.

2. Using NTLM authentication should not lead to not displaying the configured URI.

Comment 1

7 years ago
I just landed some protocol handler fixes in bug 536527 and bug 589170. I'm not 100% sure this is a duplicate but it's quite possible. Are you able to build from the svn sources and test? I'll definitely include all my fixes in the next Prism release but that might not happen right away.
(Reporter)

Comment 2

7 years ago
Thank you Matt! Alas, I don't know how to build from the svn sources - but if you have some kind of instructions for beginners?

Comment 3

7 years ago
The best we have right now is this: https://developer.mozilla.org/En/Prism/Build
(Reporter)

Comment 4

7 years ago
Hi Matt. I build Prism from the svn sources today and the problem seems to be fixed. Thanks a lot!
You need to log in before you can comment on or make changes to this bug.