Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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.

Error Messages

Not Applicable. The resulting saved file is corrupted and cannot be opened.

Steps to Reproduce

  1. Use a system that uses Encoding to send the file to a SOAP service. 
  2. use TCPMon to capture the packets before it reaches SOAP service. 
  3. Run tracer to view the pyRequestAttachmentPage page and observe the attachment values pyAttachValues(1).

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. 


This issue is resolved by hotfix item HFIX-22966.

Published July 9, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us