RT 3.2.2 CLI 'Malformed response' errors

Hi all,

I’ve just setup a brand new install of RT 3.2.2 on a Fedora Core 3
box, running apache 2.0.52-3.1, along with perl 5.8.5, & mod_perl
1.99_16-3 and it all seems to be working fine.

But I’m a happy user of the 1.0.7 stuff, and I really really really
liked the clean display and CLI interface of the 1.0.x series. So
this leads to my problem report, and my wishes.

Problem:

If I use the ‘rt’ perl tool to do a query from the command line, I
get “Malformed RT reposonse” erorrs:

# ./rt ls "Status='new'"
Password: 
rt: Malformed RT response from http://rt3.taec.toshiba.com/.
(Rerun with RTDEBUG=3 for details.)

So if I re-run with that setting it works, sorta. I know see the data
on the tickets, but it still barfs with an error:

export RTDEBUG=3

[root@rt3 bin]# ./rt ls "Status=‘new’"
Password:
POST http://rt3.taec.toshiba.com//REST/1.0/search/ticket
Content-Length: 210
Content-Type: multipart/form-data; boundary=xYzZY

–xYzZY
Content-Disposition: form-data; name=“query”

Status=‘new’
–xYzZY
Content-Disposition: form-data; name=“user”

root
–xYzZY
Content-Disposition: form-data; name=“pass”

<not for you!>
–xYzZY–
HTTP/1.1 200 OK
Connection: close
Server: Apache/2.0.52 (Fedora)
Content-Type: text/plain; charset=UTF-8
Client-Date: Thu, 16 Dec 2004 20:23:04 GMT
Client-Peer: 209.243.166.67:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked
Set-Cookie: RT_SID_TAEC.80=c3ce215060e6879467cd9b31f65a9c72; path=/

RT/3.2.2 200 Ok3: test ticket 2
4: Why aren’t tickets coming in via email?
7: test of NIS rt alias
9: test ticket
10: test ticket
11: test mail via NIS alias
12: test ticket
13: test ticket via rt@taec.com
14: I have an account
15: Why aren’t URLs in tickets working?
16: a new test ticket
rt: Malformed RT response from http://rt3.taec.toshiba.com/.

Now for my wishlist:

  1. Does anyone have a CSS to make RT 3.2 look and act more like a
    1.0.x web interface?

  2. Does anyone have a CLI tool that works more like the 1.0.x CLI
    tool? The web is nice, but it’s getting so complicated that it’s
    not worth using for smaller sites that DON’T need all the
    complexity and flexibility that RT offers now.

Thanks,
John

Toshiba America Electronic Components
john.stoffel@taec.toshiba.com

If I use the ‘rt’ perl tool to do a query from the command line, I
get “Malformed RT reposonse” erorrs:

The user you’re trying to access RT with does not have sufficient
rights. Make sure root is able to be granted rights (etc…) or give
it a username that already has sufficient rights.

Now for my wishlist:

  1. Does anyone have a CSS to make RT 3.2 look and act more like a
    1.0.x web interface?

CSS controls how it looks, not how it acts. They’ve got it to
something like 95% converted to use css, probably even more so in 3.4.

  1. Does anyone have a CLI tool that works more like the 1.0.x CLI
    tool? The web is nice, but it’s getting so complicated that it’s
    not worth using for smaller sites that DON’T need all the
    complexity and flexibility that RT offers now.

Odd… I thought it was getting less complicated, imho…

Anyway, the api is such that it would be rather easy to write a custom
cli interface.

Andy Harrison

Hi all,

If I use the ‘rt’ perl tool to do a query from the command line, I
get “Malformed RT reposonse” erorrs:

# ./rt ls "Status='new'"
Password: 
rt: Malformed RT response from http://rt3.taec.toshiba.com/.
(Rerun with RTDEBUG=3 for details.)

The following patch fixes this and will be in 3.2.3

=== html/REST/1.0/search/ticket
— html/REST/1.0/search/ticket (revision 1984)
+++ html/REST/1.0/search/ticket (local)
@@ -135,7 +135,7 @@
$output = form_compose(@output) if @output;

OUTPUT:
-$m->out(“RT/”. $RT::VERSION . " " . $status);
+$m->out(“RT/”. $RT::VERSION . " " . $status ."\n\n");

$m->out($output );
</%INIT>