Now the question is, did that fix my REST interface weirdness
as well.. probably. It's late so I'll work on that tomorrow.
So, I've been able to figure out now how to reconstruct the binary from the
Content: section in the REST response for
/REST/1.0/ticket/ticket-id/attachments/attachment-id
In the REST interface, if you make a request like:
Request: /REST/1.0/ticket/ticket-id/attachments/attachment-id
You get a response like:
RT/3.8.2 200 Ok
id: 866
Subject:
Creator: 66
Created: 2008-08-05 00:27:27
Transaction: 2467
Parent: 864
MessageId:
Filename: word.doc
ContentType:
Tom Lahti wrote:
In the REST interface, if you make a request like:
I may have stumbled into a different problem here. I recently (well, 2
weeks ago) upgraded from 3.8.0 to 3.8.2 and now all non-text attachments do
not open properly. I created a new test ticket with a new attachment, and
it
I may have stumbled into a different problem here. I recently (well, 2
weeks ago) upgraded from 3.8.0 to 3.8.2 and now all non-text attachments do
not open properly. I created a new test ticket with a new attachment, and
Nevermind, I seem to have fixed it, and am whacking myself with the Duh
