Re: [rt-users] REST API; the plus-character (+) will be not processed; plain email

2016-09-24 Thread MDroemer 
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" <lstew...@internap.com>
An: "mdroe...@gmx.de" <mdroe...@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

On Sep 20, 2016, at 9:41 AM, mdroe...@gmx.de wrote:
 

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 ®
 lstew...@internap.com[lstew...@internap.com]
 www.internap.com[http://www.internap.com]
-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017

Re: [rt-users] REST API; the plus-character (+) will be not processed; plain email

2016-09-20 Thread Landon Stewart 
On Sep 20, 2016, at 9:41 AM, mdroe...@gmx.de wrote:

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 ®
 lstew...@internap.com
 www.internap.com

-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017

[rt-users] REST API; the plus-character (+) will be not processed; plain email

2016-09-20 Thread MDroemer 
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
 
Http-Headers:
Content-Type: application/x-www-form-urlencoded; charset=utf-8
 
When we open the request-tracker web-frontend the following subject is shown:
Test '\ '
 
What we are doing wrong?
 
Thank you very much for your help.
 
Rg
Michael
-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017