Question
Phalanx Consultancy Limited
GB
Last activity: 9 May 2019 10:43 EDT
201 HTTP response code fail to interpret by Pega
Hi,
I am using Connect-SOAP to connect to a REST service via a SOA / ESB layer. SOA / ESB transforms the SOAP message to REST. Since we are using Pega 6.2, innate REST facilities are not available. Once the service is called 201 response code is received (SOA uses a PUT method). This response code is not getting interpreted by Pega and we are getting "pySOAPFaultReason Transport error: 201 Error: Created". Not sure how to debug this issue. Can anyone kindly guide?
Capgemini Financial Services
GB
Hi Manash, We also faced similar issue. Pega SR has been raised for this. Also, suggest you to upgrade your Pega Framework to Pega 7 as I am really not sure whether Pega Support REST API status code. :D
PEG
PL
As a SOAP client, Pega is not expecting HTTP response code 201. As per the SOAP Specification 201 is not one of those acceptable response codes. One small idea is to Work with the SOAP service team and have them change send back HTTP response code '200' or '202' for the successful invocation.
Newfold Digital
IN
Dear All,
Request to let me know if you found a solution for this scenario. We have exact same scenario and we are on 7.2.2. Unfortunately we are required to use a soap translation layer for the end rest services.
Appreciate your help.
Thanks,
Praneeth
Sopra Steria Group SA
FR
Hello,
I Have exactly the same kind of problem (code HTTP 404 is not interpreted, whereas 400 is interpreted)
Can you provide us an explanation ?
Thanks
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
Sopra Steria Group SA
FR
