Forum / Remote Desktop Manager - Support

Browser Protocol Extension Bug?

  • Create an Issue
  • Cancel


I'm trying to use your browser protocol extension as a browser link on a helpdesk web portal of ours to open RDM with a filter command. I noticed that if I pass in just a single word that the filter works fine, however, it doesn't work when there is a space involved, even when wrapping in quotes (just reverts to previous search). For example:

These work:
rdm://open?Filter=SingleWord

These do not:
rdm://open?Filter="Multiple Words" (encodes to: rdm://open?Filter=%22Multiple%20Words%22)
rdm://open?Filter="SingleWord"


I tried the same filter command using the cmd line utility and it works with multiple words IF I use the double quotes around the string:

These work:
> ../RemoteDesktopManager64 /Filter:SingleWord
> ../RemoteDesktopManager64 /Filter:"Multiple Words"

These do not:
> ../RemoteDesktopManager64 /Filter:Multiple Words


Am I using this wrong, or is this a bug? Would really like to get this working right.

HB

Clock13 days


Hello,

Thank you for reporting the issue, this is indeed a bug. The filter argument should work with spaces. I've opened a ticket with our engineering department.

Best regards,

Jean-Philippe Charest

signaturesignature

Clock13 days

Hello,

Spaces will now be parsed correctly, without the need of quotes, as soon as version 2019.2.22 hits.

Regards



Jonathan Del Signore
signaturesignature

Clock9 days

Thank you Jonathan! When is that one expected to be released?

Clock9 days