Outlook and processing of Asynchronous Pluggable Protocol URL
 

I created a handler to my own protocol. i registered everything in the
system.... The requirements in the specification of the project were to
make this protocol look like this:
my_protocol:///show?comething=1&something2=2 and so on. The most
problematic thing are 3 slashes which are transformed into 2 slashes by
outlook before URL is passed to my handler via shell as parameter. The
other problem is that in this case another slash is added before
question mark. anyway transformed URL looks like this:
my_protocol://show/?comething=1&something2=2. The number of slashes
after protocol name doesn't matter - you can even put 10 - it will cut
the amount of them down to 2. My question is - is there any way to
force outlook (and other MS Office applications) to leave URLs as they
are? i considered addins, macros, whatever. Anyone have some idea or
good solutio to my problem? :)
thanks in advance
bartek s.

Outlook and processing of Asynchronous Pluggable Protocol URL
 

no ideas at all?? i haven't found anything since yesterday :/
scoroop wrote:
I created a handler to my own protocol. i registered everything in the
system.... The requirements in the specification of the project were to
make this protocol look like this:
my_protocol:///show?comething=1&something2=2 and so on. The most
problematic thing are 3 slashes which are transformed into 2 slashes by
outlook before URL is passed to my handler via shell as parameter. The
other problem is that in this case another slash is added before
question mark. anyway transformed URL looks like this:
my_protocol://show/?comething=1&something2=2. The number of slashes
after protocol name doesn't matter - you can even put 10 - it will cut
the amount of them down to 2. My question is - is there any way to
force outlook (and other MS Office applications) to leave URLs as they
are? i considered addins, macros, whatever. Anyone have some idea or
good solutio to my problem? :)
thanks in advance
bartek s.