Question
EY
DE
Last activity: 9 Aug 2017 7:51 EDT
Sending REST call with attachment
Hi,
I am currently implementing a connection to a REST service and I have to send a file with the POST request. Based on other PDN articles, I learned, that I have to specify the properties .pyAttachValues(1), .pyAttachNames(1), .pyAttachTypes(1), .pyAttachFileNames(1)
The example REST request using curl is the following: curl "-F images=@<SourceFileName>.pdf" <URL>
After calling the REST method with this setting, the response from the server is <error>Image list is empty</error> but I am expecting something like {"redirect": "/manage", "submission": "10"}
Hi,
I am currently implementing a connection to a REST service and I have to send a file with the POST request. Based on other PDN articles, I learned, that I have to specify the properties .pyAttachValues(1), .pyAttachNames(1), .pyAttachTypes(1), .pyAttachFileNames(1)
The example REST request using curl is the following: curl "-F images=@<SourceFileName>.pdf" <URL>
After calling the REST method with this setting, the response from the server is <error>Image list is empty</error> but I am expecting something like {"redirect": "/manage", "submission": "10"}
Please see also attached the screenshot of my rule. All parameter in the connector request method are empty. Do I have to specify anything here? I am currently using Pega 7.3 Platform with Pega PV 7.31 on top.
Thanks and best regards,
Thomas
Accepted Solution
EY
DE
Seemed to be an issue with Base64Decode.
I have a PDF attachment, which is Base64 encoded. I tried to send it encoded and decoded by using Base64Decode method. Both did not work.
Now I tried normal Decode function. This seems to work. At least the service sends a valid response. Hope the file is not corrupted. But I can't check this, because I do not have direct access to the service.
Pegasystems Inc.
IN
Hello Thomas,
have you tested the service outside of PRPC ,is it working fine.
While invoking the service are you getting any exception kindly share us the log files .
Thanks,
Arun
EY
DE
Hi Arun,
while working outside of PRPC, the service is working fine. I am using a Python script as well as the above mentioned curl request on command line. Both are working as expected.
I am running the tracer in parallel and the tracer does not throw any errors.
Best regards,
Thomas
EY
DE
I have tested the request comming from inside of PRPC now with a mock server. This alows me to analyse the actual request.
1) It seems like, the file is attached to the call. Also the parameter for Content-Disposition, name, filename and content-type are the same as in the curl request.
2) Pega seems to specify the Header Content-Transfer-Encoding. This is not done by curl. Might this be an issue? Can I somehow remove this?
3) The Content-Length and also boundary value are different. I am using the same file for both requests. Is there any issue with the automatic encodiing of files within PRPC to Base64?
Accepted Solution
EY
DE
Seemed to be an issue with Base64Decode.
I have a PDF attachment, which is Base64 encoded. I tried to send it encoded and decoded by using Base64Decode method. Both did not work.
Now I tried normal Decode function. This seems to work. At least the service sends a valid response. Hope the file is not corrupted. But I can't check this, because I do not have direct access to the service.
Pegasystems Inc.
IN
Hello Thomas,
Enable debug for the following logger 'Rule_Obj_Activity.pyInvokeRESTConnector.Rule_Connect_REST.Action' .
Provide the screenshot of the request parameters including headers from your rest service methods tab.
Thanks,
Arun
EY
DE
Hi Arun,
many thanks for your reply. As said, I think the REST-Call itself seems to work fine now. It seems like it is no issue with the connector itself, but rather with the encoding/decoding of the value stream.
Also the logs do not show any issues.
Attached the request parameter.
Best regards,
Thomas