REST Connect request cannot modify first Content-Disposition header
When sending a Connect-REST request with attachment Pega always set first Content-Disposition header as follows.
Wed Apr 04 03:22:41 CDT 2018:INFO:--8dZGfHO7gPBZCjmgYUr04__I9QM0vQR
Content-Disposition: form-data; name="PostData"
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
{JSON request here}
--8dZGfHO7gPBZCjmgYUr04__I9QM0vQR
Content-Disposition: form-data; name="attachments"; filename="leftmenubar_bg.jpg"
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
****************
This happened because Activity: pyInvokeRESTConnector always set first entity as "PostData".
((com.pega.apache.http.entity.mime.MultipartEntity) entity).addPart("PostData", new com.pega.apache.http.entity.mime.content.StringBody(messageData));
Is there any option available to modify first Content-Disposition header ?
Pega version 7.2
Virtusa
LK
Hi Vinas,
In my case we have set the JSON from the connector rule under POST tab. We use pyRequestAttachmentPage to set the attachments and JSON message is composed using connector rule. Issue is when building the HTTP request from pyInvokeRESTConnector it takes JSON part and append it to HTTP Entity with hardcoded value "PostData" which is available as the name of Content-Disposition header.
PFA: RestConnectorHeaders