Content-Disposition: form-data; name=content
Ticket: 5702
Action: comment
Text: Adding attachment(s).
Attachment: attachment.txt
Your form is wrong.
This is a different issue than what I had, but the results of that
exercise are a ruby library which has been open-sourced. You can make
Back in February, user 'toml at bitstatement' (
http://www.gossamer-threads.com/lists/engine?user=7874;list=rt) posted a
question about interfacing with RT from Ruby via REST. That thread is
archived here:http://www.gossamer-threads.com/lists/rt/users/82898
I am having a similar problem, but when
I am pleased and excited to announce that I've been approved by ownership to
open source my ruby library for accessing the REST interface to RT.
I will release the code tomorrow when I get to the office. It will include the
XML-RPC service as well.
--
--
Tom
It also seems bizarre to me to implement the interface that way. Basically
its like making a web page with a single text area named content and then
requiring formatting within that one field. Why not have the REST interface
have discrete fields? Coding to it would be certainly be
I am working on some code in ruby that accesses the REST interface. I am
running RT 3.8.2. I am able to login, save cookies, and retrieve tickets
and history without problems.
My problem starts when I try to use REST to add a comment/correspondence to
a ticket. The following code:
Tom Lahti wrote:
I am working on some code in ruby that accesses the REST interface.
I've re-written the whole thing using the rest_client ruby gem, and
essentially the same results, but I get more info out of what's going on:
# ./resttest2.rb
- Request headers
no value sent for required parameter 'changes'
Stack:
[/opt/rt38/share/html/REST/1.0/dhandler:285]
[/opt/rt38/share/html/REST/1.0/autohandler:54]
[/opt/rt38/share/html/autohandler:311]
I seem to have figured this out. You can use
application/x-www-form-urlencoded, but you have to
