<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Based on the comments in this thread, I was able to use the following
HTML form to create a new ticket:<br>
action="<a class="moz-txt-link-freetext" href="https://support">https://support</a>.<myservernamehere>.com/REST/1.0/ticket/new/"><br>
User: <input type="text" name="user" size="20"><br><br>
Pass: <input type="text" name="pass" size="20"><br><br>
Content: <textarea rows="10" name="content" cols="30">id: new<br>
Text: This is the ticket text<br>
Subject: This is my ticket<br>
<p><input type="submit" value="Submit"
name="B1"><input type="reset" value="Reset"
Interestingly, the Queue field had to be at the end of the list or it
Thanks again for the excellent help! I'll start the integration via php
using the code Tim supplied (thanks Tim!)<br>
Frank F. Smith wrote:
<blockquote cite="mid:email@example.com" type="cite">
<pre wrap="">Tim Coles wrote:
<pre wrap="">I think simple forms fail because the REST interface is quite particular
about carriage return/line feed combinations. IIRC it requires a CF/LF
between each http field but within the http field called "content"
(where you pass it all of your ticket fields) it will just accept a \n
between each one. Something like that anyway.
Either way having or not having the right combination was the difference
between success and failure for me on several occasions (and was the
main problem our .NET devs had when doing their test forms).
<pre wrap=""><!---->Sounds about right to me, though I've not tested all the combinations.
Mike: In the sample content I sent moments ago, I failed to note that
what _I_ am sending (based on my understanding of the RT::Client::REST
modules) has CrLf after each line _except_ the field: value lines, which
all end with just Lf.