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

[MDroemer at gmx.de]

Dear RT-users,

the following solution has been implemented:
...
$http({
          url: 'http://<rt-host>/REST/1.0/ticket/new',
          method: "POST",
          headers: {'Content-Type': 'application/x-www-form-urlencoded; charset=utf-8'},
          params: { user: $scope.user, pass: $scope.pass },
          data:  'content='+$httpParamSerializerJQLike(content)+'\n'+'Queue: '+rtQueue
          })
... 

The content needs to be processed by AngularJS service $httpParamSerializerJQLike.

Now, it is working.
All special chaectors are URI-encoded.

Thank you very much for your help.

Rg
Michael
 

Gesendet: Samstag, 24. September 2016 um 11:19 Uhr
Von: MDroemer at gmx.de
An: rt-users at lists.bestpractical.com
Betreff: Aw: Re: [rt-users] REST API; the plus-character (+) will be not processed; plain email
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 at internap.com>
An: "MDroemer at gmx.de" <MDroemer at gmx.de>
Cc: "rt-users at lists.bestpractical.com" <rt-users at 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, MDroemer at 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 ®
📧 lstewart at internap.com[lstewart at internap.com]
🌍 www.internap.com[http://www.internap.com][http://www.internap.com[http://www.internap.com]]