[Mono-bugs] [Bug 762529] New: EWS exchange managed API load attachments base64 decoding gives wrong output
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Wed May 16 11:58:26 UTC 2012
https://bugzilla.novell.com/show_bug.cgi?id=762529
https://bugzilla.novell.com/show_bug.cgi?id=762529#c0
Summary: EWS exchange managed API load attachments base64
decoding gives wrong output
Classification: Mono
Product: Mono: Class Libraries
Version: 2.10.x
Platform: All
OS/Version: RHEL 5
Status: NEW
Severity: Normal
Priority: P5 - None
Component: System
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: j.belis at be.pgz.eu
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
Created an attachment (id=491069)
--> (http://bugzilla.novell.com/attachment.cgi?id=491069)
zip with test cs, attachment orginal an wrong extracted
User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64;
Trident/5.0)
Using the EWS exchange managed API on linux to extract attachments from mail
message. the returned soap message contains a base64 binary attachment that can
be saved to disk. The result file is different from the original attachment.
Some bytes are missing at position 8192. ( exact on 8K block ).
When using attachment of 18k it gives wrong output on position 8192 (8Kb),16384
(16Kb).
When there is no more 8K block in the file it gave the error on 20480. 4K block
after 16384. So it seems to indicate some function that does work with blocks
of data. Maybe decoding base64 functions.
Reproducible: Always
Steps to Reproduce:
1. csharp, exchange 2007 server
2. have 1 file in inbox with 1 mail test with 1 attachment
3. run program to extract 1 attachment from 1 test mail
Actual Results:
output file as a result of saving the attachment is wrong size and is missing
data. Result file is thus different from original attachment
Expected Results:
Same file as original attachment
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list