Dear RT-users,
thanks for your quick response.
We are using JavaScript API AngularJS and REST API to create new tickets.
There is a similar function in AngularJS, see follow:
encodeURIComponent(content);
Unfortunately it doesn’t work, also.
Using firebug the content seems fine.
That means, the submitted data stream over the network is fine.
How can i check in RT the incomming data stream from the client of the REST-API?
What we are wondering, other special characters are visbile, for example ‘?’, in a created ticket.
Thank you very much.
Rg
Michael
Gesendet: Dienstag, 20. September 2016 um 19:08 Uhr
Von: “Landon Stewart” lstewart@internap.com
An: “MDroemer@gmx.de” MDroemer@gmx.de
Cc: “rt-users@lists.bestpractical.com” rt-users@lists.bestpractical.com
Betreff: Re: [rt-users] REST API; the plus-character (+) will be not processed; plain email
Dear Request Tracker users,
while we working with special characters, we noticed that the plus-character will be not processed by the REST-API, when a new ticket is created.
All other special characters will be processed.
Here a simple content:
content=
id: ticket/new
Subject: Test ‘+’
Queue: General
You should urlencode that text:
$ perl -e ‘use URL::Encode qw/url_encode_utf8/; print url_encode_utf8(“Test +”);’
Test+%2B
The + here is the space, the %2B is the plus sign from the string.
Landon Stewart
Lead Analyst - Abuse and Security Management
INTERNAP ®
lstewart@internap.com[lstewart@internap.com]
www.internap.com[http://www.internap.com]