Question
Bank of America
US
Last activity: 8 Jan 2018 11:42 EST
Issue with launching Pega application thru url with passing parameters in HTTP POST from Non-Pega application which is getting converted to GET
Issue with launching Pega application thru url with passing parameters in HTTP POST from Non-Pega application which is failing for POST and getting coverted to GET call.
Issue is even though calling application has Form Method as POST, call is getting converted to Get and which fails when parameter length is greater than 3000 characters.
Below is snippet of calling application
Calling Non-Pega Application
<FORM id="clientformid" name="clientform" action="PEGA APP URL" method="POST">
<INPUT type="hidden" name="pyActivity" value="PegaClassName.PegaLaunchActivityName" />
<INPUT type="hidden" name="CaseData" value="Looong Test 3500 characters … “>
</FORM>
<SCRIPT type="text/javascript">
document.getElementById("clientformid").submit();
</SCRIPT>
According to fiddler logs
1. First Call shows request header with POST
2. It gets HttpStatus as 303
3. Very next call shows Request header as GET
***Edited by Moderator Marissa to add SR Details***
JPMorgan Chase & Company
US
Hi,
It's an expected behaviour once application send the request in POST, pega application will redirect the request and get the details in GET request. You can also check the same at time of accessing pega application directly.
Pegasystems Inc.
US
Can you please further describe your use case? What are you attempting to do with the POST to Pega from the calling? Is this something that could be handled by a REST service (such as a case item being created) or another route?
You provided the following via an SR (which was redirected to the support community as design help)
1. create test html page with below code
<FORM id="FORMID" name="FORMNAME" action="PEGA APP URL" method="POST">
<INPUT type="hidden" name="pyActivity" value="PegaClassName.PegaLaunchActivityName" />
<INPUT type="hidden" name="CaseData" value="Looong json text with 3500 characters … “>
</FORM>
<SCRIPT type="text/javascript">
document.getElementById("FORMID").submit();
</SCRIPT>
Bank of America
US
We have a requirement where user can initiate a case in non-pega application and then pass captured information to pega application for further processing. Pega application creates case based on information received, launches harness, user can carry forward work on pega application to complete case flow.
Pegasystems Inc.
US
To elaborate:
The Pega application follows the standards of HTTP Clients, including web browsers, that when redirected via a 300-level HTTP response code, the request to the endpoint specified in the location header will be a GET instead of a POST.
One of the main benefits is that your client (Pega, the browser, etc) will avoid POST-ing data to the endpoint you did not intend it for. Otherwise, someone could hijack a popular service and do redirects to a malicious service in order to steal data.
Stack Exchange post about this: https://softwareengineering.stackexchange.com/questions/99894/why-doesnt-http-have-post-redirect
Telekom
DE
Hi @RiddhiCS
Well I do not have a solution for you post. I have my own question. It seems like you might know it.
I have the same requirement but the otherway around. The Pega application has to launch non pega app using a URL and pass info over POST. How to you achive this in PEGA?
Please let me know if you have any idea about it.
Bank of America
US
You can launch a modal popup or launch a new window which launches a section (either through Flow Action or Open URL in window) and uncheck "Auto-generated HTML" in the section in the HTML tab and you can specify your own HTML in there and launch non pega application from Form action.