It seems as though SelfService cannot properly handle binary attachments like Word or Excel documents. I keep getting back mangled data (sometimes they won’t even load into the application, other times the data is just way off). Is there something wrong with the encoding? The main RT area doesn’t have this issue.
Was there maybe a patch for this?
Paul
To give a little more detail, this seems to happen for subsequent requests within the same session. It looks like the first ticket created in a session has the attachment come through fine. But any other created tickets within the session are mangled. Any ideas?
Paul
Sounds like you’re running with a version of perl before 5.8.3. The
correct fix is to upgrade to perl 5.8.3On Feb 27, 2004, at 4:31 PM, Paul Barmaksezian wrote:
To give a little more detail, this seems to happen for subsequent
requests within the same session. It looks like the first ticket
created in a session has the attachment come through fine. But any
other created tickets within the session are mangled. Any ideas?Paul
-----Original Message-----
From: Paul Barmaksezian
Sent: Friday, February 27, 2004 12:50 PM
To: rt-users@lists.bestpractical.com
Subject: Mangled Attachments in SelfServiceIt seems as though SelfService cannot properly handle binary
attachments like Word or Excel documents. I keep getting back mangled
data (sometimes they won’t even load into the application, other times
the data is just way off). Is there something wrong with the
encoding? The main RT area doesn’t have this issue.Was there maybe a patch for this?
Paul
rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users ArchivesHave you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
PGP.sig (186 Bytes)
Well, we’re on 5.8.0 and I don’t think there is much of a difference, is there? Plus, why would it work in the main area of RT and not SelfService? And why would it work on the first ticket in a session on not the subsequent tickets?
Maybe there is something 5.8.3 that deals with sessions? Never heard of it …
PaulFrom: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Friday, February 27, 2004 1:35 PM
To: Paul Barmaksezian
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] RE: Mangled Attachments in SelfService
Sounds like you’re running with a version of perl before 5.8.3. The
correct fix is to upgrade to perl 5.8.3
You need Perl 5.8.3.
If you did a search of the list archives you wouldn’t
even be asking the question.
-ToddOn Fri, Feb 27, 2004 at 01:40:13PM -0800, Paul Barmaksezian wrote:
Well, we’re on 5.8.0 and I don’t think there is much of a difference, is there? Plus, why would it work in the main area of RT and not SelfService? And why would it work on the first ticket in a session on not the subsequent tickets?
Maybe there is something 5.8.3 that deals with sessions? Never heard of it …
Paul
-----Original Message-----
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Friday, February 27, 2004 1:35 PM
To: Paul Barmaksezian
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] RE: Mangled Attachments in SelfServiceSounds like you’re running with a version of perl before 5.8.3. The
correct fix is to upgrade to perl 5.8.3On Feb 27, 2004, at 4:31 PM, Paul Barmaksezian wrote:
To give a little more detail, this seems to happen for subsequent
requests within the same session.� It looks like the first ticket
created in a session has the attachment come through fine.� But any
other created tickets within the session are mangled.� Any ideas?Paul
�-----Original Message-----
From: � Paul Barmaksezian�
Sent:�� Friday, February 27, 2004 12:50 PM
To:���� rt-users@lists.bestpractical.com
Subject:������� Mangled Attachments in SelfServiceIt seems as though SelfService cannot properly handle binary
attachments like Word or Excel documents.� I keep getting back mangled
data (sometimes they won’t even load into the application, other times
the data is just way off).� Is there something wrong with the
encoding?� The main RT area doesn’t have this issue.Was there maybe a patch for this?
Paul
rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users ArchivesHave you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users ArchivesHave you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
I take it back - maybe it is perl. I looked up the docs on 5.8.3 and it does say something about utf8:
Using substr() on a UTF8 string could cause subsequent accesses on that string to return garbage. This was due to incorrect UTF8 offsets being cached, and is now fixed.
Can some one confirm this is the issue?
PaulFrom: Paul Barmaksezian
Sent: Friday, February 27, 2004 1:40 PM
To: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] RE: Mangled Attachments in SelfService
Well, we’re on 5.8.0 and I don’t think there is much of a difference, is there? Plus, why would it work in the main area of RT and not SelfService? And why would it work on the first ticket in a session on not the subsequent tickets?
Maybe there is something 5.8.3 that deals with sessions? Never heard of it …
Paul
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Friday, February 27, 2004 1:35 PM
To: Paul Barmaksezian
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] RE: Mangled Attachments in SelfService
Sounds like you’re running with a version of perl before 5.8.3. The
correct fix is to upgrade to perl 5.8.3
Paul Barmaksezian wrote:
Well, we’re on 5.8.0 and I don’t think there is much of a difference,
is there?
THe bug you are seeing is very likely caused by a bug in Perl’s join
which was fixed in 5.8.3. At least 5.8.3 fixes the symptoms you
describe for everyone else. 
Current mail filters: many dial-up/DSL/cable modem hosts, and the
following domains: atlas.cz, bigpond.com, freenet.de, hotmail.com,
libero.it, netscape.net, postino.it, tiscali.co.uk, tiscali.cz,
tiscali.it, voila.fr, wanadoo.fr, yahoo.com.
Well, we’re on 5.8.0 and I don’t think there is much of a difference,
is there?
Except about a year of bug fixes, including some bug fixes to unicode
handling.
PGP.sig (186 Bytes)