[rt-users] URL double encoding from the custom field value

[Dalal, Kamber Z]

Kevin,

My Custom Field value is:

srch=abcd&earliest=klmtime&latest=xyztime


In the Custom Field definition link value to is set as:
http://myweb.domain.com/__CustomField__

The URL being generated is http://myweb.domain.com/srch%3Dabcd%26earliest%3Dklmtime%26latest%3Dxyztime

Instead of what should be:

http://myweb.domain.com/srch=abcd&earliest=klmtime&latest=xyztime

Thank you for the assistance.

Kamber Dalal


From: Dalal, Kamber Z
Sent: Thursday, February 13, 2014 13:33
To: 'rt-users at lists.bestpractical.com'
Subject: URL double encoding from the custom field value



RT version 4.0.5
Issue:

Custom field value gets URL double encoded for custom field that has link values to set up to Splunk ES incident review.
The '=' changes to %3D and the '&' becomes %26, from the custom field's value.  In the ticket display the value of the custom field displays '=' and '&' fine, but the link translates it to '%3D' and '%26'

Need help in preventing the double encoding.

Thank you,
Kamber Dalal


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20140214/fbae0ba5/attachment.htm>