XMPP URI's on Windows
Fluteman
WooyoTiNewe at mindspring.com
Wed Aug 13 06:18:23 EDT 2014
I'm entering this from left field, and maybe this is the blind
suggesting something to the blind (since you're on Win 7 and I'm on
WinXP), but here's what I tried when looking into the MIME association
for xmpp in the Registry:
Take Tres' suggested command prompt query "reg query "HKCR\xmpp" /ve",
and change the /ve parameter to /s, thusly:
reg query "HKCR\xmpp" /s
Here's what I got from that:
~~~~~~~~~~
HKEY_CLASSES_ROOT\xmpp
<NO NAME> REG_SZ URL:xmpp
URL Protocol REG_SZ
HKEY_CLASSES_ROOT\xmpp\DefaultIcon
<NO NAME> REG_SZ C:\Program Files\Pidgin\pidgin.exe
HKEY_CLASSES_ROOT\xmpp\shell
<NO NAME> REG_SZ
HKEY_CLASSES_ROOT\xmpp\shell\Open
<NO NAME> REG_SZ
HKEY_CLASSES_ROOT\xmpp\shell\Open\command
<NO NAME> REG_SZ C:\Program Files\Pidgin\pidgin.exe
--protocolhandler=%1
~~~~~~~~~~
The value of importance on my system is the "no name" value in the
subkey "Open\command" which launches Pidgin to handle the xmpp protocol.
So I'm suggesting you use the /s parameter of the "reg" command on your
system to see all the subkeys and values under HKCR\xmpp. I suspect
you'll find something similar; the thing to look for is whether it is
Pidgin registered to handle xmpp, or some other program.
One possible reason I could think that it may be wrong is if you have
any of your web browsers (IE, Chrome, Firefox etc.) set to insure that
they are *the* default web browser every time they start. (Just
guessing.) But if one of your browsers is overriding Pidgin, you may
need to turn of that "check I'm the one every time you run me" setting
in your browser. If you find you need to do this, then - guessing again
- you'd then need to re-install Pidgin to have the Pidgin installer
point all the "chat" URL handlers back to Pidgin in the Registry.
P.S. I found a useful web page about this:
http://blogs.msdn.com/b/ieinternals/archive/2011/07/14/url-protocols-application-protocols-and-asynchronous-pluggable-protocols-oh-my.aspx
...look in the subsection titled "Application Protocols" to see how this
might vary from one Windows version to another. There is also a section
titled "Warning: Redirects to Application Protocols will not function"
which says that if your browser is an older version of IE, protocol
handling via an external program (i.e., Pidgin) will fail. They give a
workaround, but it doesn't look great.
--Scott
Zach Seils wrote:
>
> Thanks for continuing to look into this. Of you're saying that I
> need to be logged in and active on an XMPP service, then that's
> already the case.
>
> The last registry entry you sent appears to be specific to Windows
> 8. I'm running Windows 7.
>
> Zach
>
> On Aug 12, 2014 8:42 PM, "Tres Finocchiaro" wrote:
>
> I spent some time reproducing your issue. Â It appears Pidgin will
> not respond to the URI request unless the XMPP service that you
> have is valid, online and enabled. Â So just sign in with a valid
> XMPP account and the popup will work.
>
> -Tres
>
>
>
> <mailto:Tres.Finocchiaro at gmail.com>
>
>
> On Tue, Aug 12, 2014 at 5:48 PM, Zach Seils wrote:
>
> Thanks for the response. Here is the output from my system:
>
> C:\>reg query "HKCR\xmpp" /ve
>
> HKEY_CLASSES_ROOT\xmpp
> Â Â Â (Default)Â Â Â REG_SZÂ Â Â URL:xmpp
>
>
> C:\>reg query "HKCU\Software\Microsoft\Internet
> Explorer\ProtocolExecute\xmpp" /v WarnOnOpen
> ERROR: The system was unable to find the specified registry
> key or value.
>
> C:\>reg query
> "HKCU\Software\Microsoft\Windows\CurrentVersion\ApplicationAssociationToasts"
> /v xmpp_xmpp
> ERROR: The system was unable to find the specified registry
> key or value.
>
> Does the second output matter if I don't use IE as my browser?
>
> I'm assuming the third error means I am missing something?Â
> Are these values set as part of the Pidgin installation?
>
> Zach
>
>
>
> On Tue, Aug 12, 2014 at 12:06 PM, Tres Finocchiaro wrote:
>
> @Zach,
>
> I tried your link and it works fine for me.
>
> If you are comfortable doing so, perhaps you could quickly
> check the registry using Command Prompt:
>
>
> *reg query "HKCR\xmpp" /ve*Â
>
> /*(for me shows "URL:xmpp")*Â /
>
> Â
>
> *reg query "HKCU\Software\Microsoft\Internet
> Explorer\ProtocolExecute\xmpp" /v WarnOnOpen
> /(for me shows 0x0)/*/Â /
>
> Â
>
> *reg query
> "HKCU\Software\Microsoft\Windows\CurrentVersion\ApplicationAssociationToasts"
> /v xmpp_xmpp
> /(for me shows 0x0)/*
>
>
> Perhaps you have another mime handler associated with xmpp
> protocol?
>
>
>
> <mailto:Tres.Finocchiaro at gmail.com>
>
>
> On Tue, Aug 12, 2014 at 9:45 AM, Zach Seils wrote:
>
> Hello,
>
>
> I'm using Pidgin 2.10.9 on Windows 7. When I click
> on an XMPP link in a web browser, it does not launch a
> new message window. The only thing printed in the
> Debug Window is 'winpidgin: Got external Buddy List
> focus request.'Â The format of the link is
> xmpp:user at domain.com?message
> <http://xmpp:user@domain.com?message>. I verified
> the browser and OS app association for xmpp. Any
> suggestions where to look next?
>
> Thanks,
> Zach
>
>
> _______________________________________________
> Support at pidgin.im <mailto:Support at pidgin.im> mailing list
> Want to unsubscribe? Â Use this link:
> https://pidgin.im/cgi-bin/mailman/listinfo/support
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Support at pidgin.im mailing list
> Want to unsubscribe? Use this link:
> https://pidgin.im/cgi-bin/mailman/listinfo/support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pidgin.im/pipermail/support/attachments/20140813/98f2202b/attachment.html>
More information about the Support
mailing list