Support Article
Connect-HTTP URL encoding problem due to special char
SA-19964
Summary
User recently upgraded their application from PRPC 6.2 to PRPC 7.1.8. After the upgrade, users are not able to upload the documents to filenet as Connect-HTTP is trimming the file name passed as Query string parameter. It is trimming anything that comes after "&" in file name. It looks like Connect-HTTP input parameters are not properly encoded if the parameter value contains special character. This is working fine in PRPC 6.2. User tested by doing a private check out of 6.x version of the 'InvokeHTTPConnector' activity to make sure that issue is pertaining to PRPC 7.1.8 and they confirmed it.
Error Messages
Not Applicable
Steps to Reproduce
- From an activity, invoke Connect-HTTP rule.
- Input for the parameter contains an special character for example, "&".
- Pega is not encoding the parameter for http request correctly. Pega is ignoring the special character and trims anything after the ampersand.
Root Cause
A defect in Pegasystems’ code or rules is identified as a root cause of this issue.
Resolution
Perform the following local-change:
- Override the "InvokeHTTPConnector" activity and update the Java code in step #3 of this activity. Please contact Pega GCS to get the modified code (ask HTTPStep3716Final.txt) for step #3 of this activity.
Published February 22, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.