Service-SOAP corrupts received SOAP request attachments
When sending a PDF as attachments to Pega SOAP Service from an external Drupal website, the file gains extra null character causing it to be corrupted and unopenable. This occurs when using "Content-Transfer-Encoding: base64" with a content type of PDF: Content-Type: application/pdf;
This is not reproduced when using SoapUI configured with Content-Transfer-Encoding: binary.
Not Applicable. The resulting saved file is corrupted and cannot be opened.
Steps to Reproduce
- Use a system that uses Encoding to send the file to a SOAP service.
- use TCPMon to capture the packets before it reaches SOAP service.
- Run tracer to view the pyRequestAttachmentPage page and observe the attachment values pyAttachValues(1).
The root cause of this problem is a defect in Pegasystems’ code/rules.
This issue is resolved by hotfix item HFIX-22966.
0% found this useful