mailto: Custom URI scheme

Have web application with two different type of customers. IN customer deail page generating links
on email addresses to click and open 'compose new mail' window of my mail program, but need to open
different mail program for each type of customer. Decided to create different URI scheme for each
type of customer.

Have created custom URI scheme by this instructions
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

In web application creating links in such manner: a
href="custom_protocol_name:email_address"email_ad dress/a

it does work fine, proper email program open by clicking but windows URI handler for some reason
send full string "custom_protocol_name:email_address"in a %1 parameter, not only 'email_address' as
expect. Seem URI handler does not consider semicolon as a delimiter as in case of use standard
'mailto:' URI.

Am I doing something wrong?

L.

On Sun, 11 Oct 2015 13:02:48 +0200, Petr Laznovsky wrote:
Have web application with two different type of customers. IN customer deail page generating links
on email addresses to click and open 'compose new mail' window of my mail program, but need to open
different mail program for each type of customer. Decided to create different URI scheme for each
type of customer.

Have created custom URI scheme by this instructions
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

In web application creating links in such manner: a
href="custom_protocol_name:email_address"email_ad dress/a

it does work fine, proper email program open by clicking but windows URI handler for some reason
send full string "custom_protocol_name:email_address"in a %1 parameter, not only 'email_address' as
expect. Seem URI handler does not consider semicolon as a delimiter as in case of use standard
'mailto:' URI.

Am I doing something wrong?

L.

That's how it works. The URI will always include the protocol itself.

Imagine if it's not...
Instead of email clients, let's assume them as web browsers.
So if the protocol is not included, how will the browser know whether to
access the site using HTTP or HTTPS?

In your case, I suggest make a program (or VBS) to handle all of your custom
protocols, where it will decide which application to execute from given
protocol.

That's how it works. The URI will always include the protocol itself.

Imagine if it's not...

Expecting some parsing on OS side, the name of protocol put into %1 and its value into %2 or
somethig, but nevermind. Will do it somehow.... Thanks for info.


L.