HTTP Post using HTTPConnector is not working
SummaryUser is using a CONNECT-HTTP rule to perform an HTTP 'POST' action against a Microsoft SQL Server Reporting Services ('SSRS') endpoint.
The format of the URL needed by this endpoint includes HTTP Query String components which are NOT composed of name/value pairs.
As opposed to a more typical name/value pair style Query String like this:
The CONNECT-HTTP rule was shown to be stripping out the non key-pair values from the URL; so the first URL above would be converted to:
Error MessagesNot Applicable. The URL sent is still syntactically correct – but the endpoint will deliver the incorrect response.
Steps to ReproduceConfigure a CONNECT-HTTP Rule that includes (say) a Query String of '?/topfolder/'.
It makes no difference whether this is defined on the 'Endpoint URL' field or under the 'Resource path' field.
Note also: it is not possible to do this on the 'Request' Tab (under 'Query String Parameters') – since this form only supports name/value pairs as components for the Query String.
Root CauseA defect in Pegasystems’ code or rules.
HTTP-CONNECTOR does not allow to construct this form of URL.The Query Parameter string that contains straight-forward values/path style; rather than the more usual 'name=value' pairs
ResolutionPerform the following local-change: use a CONNECT-REST rule instead of a CONNECT-HTTP rule.
Published June 2, 2017 - Updated July 27, 2017