Question

6
Replies
920
Views
JohnF575 Member since 2017 2 posts
Liberty Global Europe Ltd
Posted: May 25, 2018
Last activity: May 30, 2018
Closed

Connect REST query string parameter encoding not working for semicolon

I have a requirement to send a query string parameter that includes semicolons to separate values like so:

https://endpoint/getInfo?propertynames=propname1;propname2;propname2

I am encoding the parameter using the function @encodeURLParameter and I can see in the tracer that this is working and on the connect rest rule I have also set Content-Type header to be application/x-www-form-urlencoded.

However when the endpoint receives the request the querystring parameter is no longer encoded and the semicolons are in plain text.

Data Integration
Moderation Team has archived post
Share this page LinkedIn