View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022439 | mantisbt | api soap | public | 2017-02-28 15:00 | 2017-03-22 03:53 |
Reporter | info4km | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 1.2.19 | ||||
Summary | 0022439: mc_issue_attachment_add seems to be adding corrupt files through web services api | ||||
Description | attachments can't be opened. It says they are corrupt or too large. When you open them they look like data. See the Additional Information field for this issue. | ||||
Additional Information | I see issues similar to this in the mantisbt.org bugtracker. We have a salesforce system that our customers use to enter tickets. We sync them up to mantis by creating issues in mantis for development/testing and adding notes and attachments from the original salesforce DB. We use the mantis soap api for this. It used to work perfectly fine, but I just found out that the attachments have been corrupted for a long time. I saw an issue similar to this that said the attachments may be encrypted when they are added. Is there something I need to do to make sure they are not encrypted when adding them or something. Can't figure out what is going wrong. All of the files look like pure data when you look in them. Linux command line shows ASCII text, with very long lines, with no line terminators. I did send mail to the mailing list for this as well. | ||||
Tags | No tags attached. | ||||
references ?
This begs the question, can you identify what has changed between then & now ? Mantis upgrade, system changes, new version of SalesForce, modified SOAP API script... Are you storing attachments in DB or disk ? Looking at the attachment you sent to the mailing list (bugfiletable.doc, February 27, 2017 11:28 AM), it seems the BLOBs are 2 bytes long which does not match the filesize. What RDBMS do you use ? Can you reproduce the issue
For the record, 1.2.19 is no longer supported, so if this turns out to be a bug in the SOAP API I would ask you to check if it can be reproduced in 1.3.x / 2.x, and it would only be fixed there |
|
info4km, You did not provide any feedback; I am therefore resolving this issue as "no change required". Feel free to reopen the issue at a later time and provide the requested information. |
|