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

Unable to send mutilpart request via connect REST



Using PEGA unable to make multipart or form-data requests.

​When attachments are available PEGA is automatically converting request to multipart content type. But when no attachments are being sent, multipart request is not being generated.

User would like to generate a multi-part request, without attachments.

Error Messages

401 error BAD REQUEST this is returned from the source system.

Steps to Reproduce

1. Create a Connect REST rule to access a service which supports multi-part request.
2. Generate a multi-part request to send data to the service.

Root Cause

This issue was determined to be a product enhancement request. 


An enhancement request, FDBK-15928, has been created for consideration by Pega Product Management. 
Explained the user that changes are available in Pega 7.2 and also available as a hotfix in 7.1.9.



Published July 26, 2016 - 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