New issue
Advanced search Search tips

Issue 616170 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 560809
Owner: ----
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome not honoring custom protocol handlers

Reported by casp...@gmail.com, May 31 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Example URL:
jnlp://www.java.com/ga/applet/verify/JavaDetection_applet.jnlp

Steps to reproduce the problem:
1. On Windows, install Oracle Java from here: http://www.java.com

2. Open Chrome

3. Enter this URL (below). Notice the custom protocol (JNLP). This protocol is registered during the Java installation.

  jnlp://www.java.com/ga/applet/verify/JavaDetection_applet.jnlp

This works correctly in Internet Explorer 11, Firefox 46.0.1

What is the expected behavior?
Java Web Start application should be launched. In this example, only a small window will be opened and presented on the upper left corner of the screen. You can close the app by clicking on the X. In the case of Chrome nothing happens because you are redirected to Google instead of starting the app.

What went wrong?
Chrome improperly interprets the URL as a search string and ignores the protocol "jnlp://" or "jnlps://".  Others are reporting the same with Skype and various other protocols, so this isn't a "Java" issue.  The following was closed as "Fixed", therefore this new issue was created.

https://bugs.chromium.org/p/chromium/issues/detail?id=378576

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0
 

Comment 1 by mef@chromium.org, May 31 2016

Cc: mge...@chromium.org
Components: UI>Browser>Navigation

Comment 2 by mef@chromium.org, May 31 2016

Seems to be Windows - specific interaction with system-installed custom protocol handlers.
Components: -Internals>Network
A related issue is at: https://bugs.chromium.org/p/chromium/issues/detail?id=560809
Removing internals->network as a component since the root cause does not look to be networking related.

Comment 4 by casp...@gmail.com, Jun 9 2016

It is important to note that "jnlp" now includes two protocols:

  jnlp://
  jnlps://

Both need to launch Java jnlp files with limited user intervention.

Cc: -mge...@chromium.org

Comment 6 by casp...@gmail.com, Jun 21 2016

This continues to reproduce with Chrome 51.0.2704.103 m

Anyone have any thoughts on this issue?  Getting this fixed soon would be great.
Is there any chance this will be fixed? This is a serious blocker in moving from Applets to JNLP. 
Cc: pkasting@chromium.org
Do omnibox-triggered navigations offer an infobar to launch the affected URL?  If yes, does using the infobar cause future attempts to use this protocol to work?
Mergedinto: 560809
Status: Duplicate (was: Unconfirmed)
Actually I think  bug 560809  is a superset of this.

Sign in to add a comment