2
1
I've successfully created and registered a custom protocol handler in my web application and it's working fine in all browsers. There's the initial warning dialog about launching an external application which is fine.
However when the app is deployed and the site is running under SSL, the custom protocol links no longer work in Chrome. I see the following message appears in the Developer Tools console:
[blocked] The page at https://my.site.com/path/to/page ran insecure content from iwd:-action=myaction
The same links work fine in Internet Explorer and Firefox.
Any ideas as to how to make this work? My external application by the way is a console application that's installed on the client.
edit: One extra important piece of information is that the link specifies a target which is a hidden iframe on the same page.
1Glad to see I'm not the only one to run into this very same issue. Doesn't it seem like a bug in Chrome v30 though? Unless there is some way for a custom protocol handler to be designed as "secure" then this breaks anything that uses a custom protocol handler in an iframe of a secure page. – Ron Michael Zettlemoyer – 2013-10-09T14:24:06.390
Can you elaborate as to how you did this? I am having the same problem. – Brian McGinity – 2013-10-17T08:08:03.663
@BrianMcGinity I've edited the answer to provide the javascript code – Catch22 – 2013-10-17T11:34:10.643
Thank you, looks great. Do you have problems when the SRC of iframe is more than 2000 or so characters? I would like to pass 10k or more to a vbscript. When I pass lots of data, it just dies. – Brian McGinity – 2013-10-18T01:15:54.050
I figured out 2083 is the documented max. Wonder if it possible for the executable to call a js function in the html page? – Brian McGinity – 2013-10-18T02:19:47.983
There's an active bug in Chrome for this issue:
https://code.google.com/p/chromium/issues/detail?id=318788