If you guys could file a bug report, that'd be great.
Thanks.
On Fri 29.Oct'10 at 12:44:46 -0700, Tom Lahti wrote:
Jesse's intent for the REST interface was to be RFC822 compliant, and that
ain't. So I while I could probably make rt-client tolerate it, I probably
should push this to
I fixed the issue on the client side (rt-client in ruby). It should
be fixed on the server side but I am not intimate enough for the RT
code to propose a fix.
In rt-client / client.rb / get_attachment, I replaced
headers = TMail::Mail.parse(resp)
with
resp.gsub!(/(id:\s.*\n)\n/,'\1')
Jesse's intent for the REST interface was to be RFC822 compliant, and that
ain't. So I while I could probably make rt-client tolerate it, I probably
should push this to Jesse as REST isn't working the way he intended in this
case. It will probably cause issues with other systems that
Agreed.
My fix is just temporary for someone else that could encounter the
same issue now. The real fix should be on the RT side.
I am not familiar enough with the RT stack to find where the issue is.
When I print the attachment subject from Perl, it does wrap on two
lines. Maybe the issue is
Another piece of info, the filename is 111 character long.
Thierry
Here are few more details.
The web interface access to this attachment works fine. Looking at
the full header under Ticket/Display.html?ShowHeaders=1;id=123 shows
the subject in one line. And I can download the attachment fine.
But if I call REST/1.0/ticket/123/attachments/1302 then the
