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

Kevin Falcone falcone at bestpractical.com
Thu Feb 13 16:25:03 EST 2014

On Thu, Feb 13, 2014 at 02:33:02PM -0500, Dalal, Kamber Z wrote:
>    RT version 4.0.5
>    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'

This question really needs replication steps.

Create a custom field with these settings
Put this in Link value to
Create a ticket where the custom field has this specific value
visit Ticket/Display.html and click on the link and this will break
with X

Without it, I'm really guessing at what and where is double encoding.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20140213/2cbfb61a/attachment.sig>

More information about the rt-users mailing list