Multipart Connect-Rest post request
Hi,
For one of our requirement, we need to send zip files to client along with json data in Connect-Rest post request. Below is the request format we need to send
metadata:
body:
{
"personId":"personId",
"documentType":"DISPUTES",
"documentTitle":"response",
"description":"blah blah",
"caseId":"pega",
"agentUserId":"name of the agent that uploads the document",
"inboundChannel":"NETWORK"
}
file:
For json data, I have created the data transform and mapping the request and for file data I am setting properties ".pyAttachNames to file, .pyAttachTypes to zip, .pyAttachValues to attach stream and .pyAttachFileNames to actual filename with extension" in pyRequestAttachmentPage.
In Connect-Rest rule post method, I am mapping request from clipboard property .request.body_POST, however i am getting 400 bad request error when the rest rule is invoked. When i checked log after setting loggers i can see below messages
Adding outbound message data to the POST request
Request attachment page detected. Attemtping to construct multipart message.
Multipart request message has been constructed.
Request message size is 24850 bytes.
HTTP Status code: 400 Bad Request
It would be helpful if anyone knows how to debug and correct the issue.
Thanks for the reply AdamKraus.
After enabling the log, please finde the request and response
------------------HTTP REQUEST CONTENTS------------------POST /api/case/v1/documents?tenantId HTTP/1.1
Request Headers: {Content-Type=multipart/form-data; boundary=TGLIYeDKiCVO6SZuKUPZYqAxY4YfMCfU}
Request Message Data: 25584 bytes to be sent
<?xml version="1.0"?>
<pagedata>
<pxObjClass>GS-Int-SendMComDoc-UpdateDocLib</pxObjClass>
<agentUserId>SmartDispute</agentUserId>
<documentType>DISPUTES</documentType>
<caseId>D-1205</caseId>
<description>Representment Doc</description>
<personId>58f7c2be-2cc4-4132-9477-b5251daca351</personId>
<inboundChannel>NETWORK</inboundChannel>
<documentTitle>response</documentTitle>
</pagedata>
----------------END HTTP REQUEST CONTENTS----------------
2018-10-30 10:32:26,972 [tp-apr-8080-exec-260] [TABTHREAD2] [ ] [ MCardDev:01.01.01] ( connect.rest.RESTConnector) INFO gldsch-gsdisp-dt1.pegacloud.net|106.206.96.93|Rule-Connect-REST.GS-Int-SendMComDoc-UpdateDocLibAPI.UpdateDocLib ganesh.bhat@in.pega.com - HTTP Status code: 400 Bad Request
2018-10-30 10:32:26,972 [tp-apr-8080-exec-260] [TABTHREAD2] [ ] [ MCardDev:01.01.01] ( connect.rest.RESTConnector) DEBUG gldsch-gsdisp-dt1.pegacloud.net|106.206.96.93|Rule-Connect-REST.GS-Int-SendMComDoc-UpdateDocLibAPI.UpdateDocLib ganesh.bhat@in.pega.com -
------------------HTTP RESPONSE CONTENTS------------------
Response Headers:
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Connection: keep-alive
Date: Tue, 30 Oct 2018 10:32:26 GMT
Expires: 0
Pragma: no-cache
Server: nginx
Set-Cookie: AWSALB=vERpq+xxQ90OLsQV824pbVvo3A6/vYUQ9d576Vmnlnxka1/FMFi1sy1ZUUPWMFJ3txqaQwvJG8yiOjJu/4G2qbnme3F1iD5i1rfVKrWjK9t7fGHDbYBTb0P2d6C1; Expires=Tue, 06 Nov 2018 10:32:26 GMT; Path=/
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
Transfer-Encoding: chunked
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
Response Message Data: 0 bytes received
----------------END HTTP RESPONSE CONTENTS----------------
400 means the server doesn't understand the request. You'll want to look at the exact request Pega's actually sending to figure out if something is wrong with the request, and if so what. If you're in Pega 7.3.1+ you can use these loggers, set to DEBUG, to log it to the RULES log: httpclient.wire.content and httpclient.wire.header . If you're on an earlier version you'll need to take a network trace with something like TCPMon.
If the output is what you're expecting, it's an issue at the endpoint. If it's not, post the log snippet with the actual request here and I'll try to take a look.