"URL" Mapper/Encoder

Hi Alumio,

I’d love a “URL” encoder/mapper. There’s already the “Form URL serializer”, but that works differently (a space becomes a + instead of %20, etc.).

The use-case for this is that there are a few systems requiring you to send a JSON inside the URL, but specifically inside a particular parameter. That’s currently impossible to combine within the HTTP Transformer.

Workaround for now is just creating the filterstring yourself and pasting that into the HTTP Transformer, but that’s not that great for readability.

Hi Floris,

Thank you for your feedback. I believe that it would help the other users too when it comes to the same case you are dealing with.

Let me pass this on to the team and discuss the possibility to implement the encoding option. I’ll be sure to let you know once I have an update.

If you have any other feedback, feel free to share it with us again. Once again, thank you very much for your feedback.

Hi Floris,

We would like to inform you that we decided to create a story to implement such a feature. In this case, we are going to add options to the “Form URL encoded” encoder or serializer so that you can choose to encode space to “+” (RFC 1738 - Uniform Resource Locators (URL) (RFC1738)) or encode space to “%20” (RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax (RFC3986)).

At the moment, we cannot give you any estimation of when the feature will be available in the future. However, once it is released, we will be sure to include it in our Release notes.

Feel free to let us know if you have any other feedback.