URL copied into service node changes when colon is present

[sameera.tumuluri]

In the recent times we have been observing some URL’s change after saving the definition in service node. For example:

https://api.telegram.org/bot6089913040:AAFpugTFeOOw5fnE5v-Ug9ACoCf9lQPrZDI

after saving into a service node changes to:

https://api.telegram.org:I/bot6089913040:AAFpugTFeOOw5fnE5v-Ug9ACoCf9lQPrZDI

The :I character gets added to the URL. This is because we are currently not supporting using colons directly in service node URL since using colons (:) in URLs can create some issues, as colons have special meaning in URLs, typically used to separate the protocol.

Solution for such URLs :-
We can create variables under environment or content variables in platform and use that variable in the service node.

Hope this helps!!

[swagata.sengupta (Swagat)]

Service Node - Passing url query parameters as encoded

@nehamsheikh @yogaramya.mendu We recommend using encodeURIcomponent to fully encode the URL if needed. Construct the API end point and query parameters dynamically in a script node. Encode the content fully in a context variable in that script node. var encodedURL = encodeURIComponent("https://abc.com/endpoint?q=[abc_def]); context.encodedURLToUseInServiceNode = encodedURL Use the context variable in the service node GET/POST {{context.encodedURLToUseInServiceNode}} configure the headers…

Another possible alternative. Whichever is more convenient.