HTTP Request action not URL encoding variables
Posted: 22 May 2013 20:20
Hi,
Just getting into this really cool tool, but have found what I believe to be a bug.
I created a simple flow to forward any received SMS to Prowl using an HTTP request action. While testing I was only using the word "test" (no quotes) but when I sent a text more than one word in, e.g. "This is a test", the flow errors.
Examining the log reveals an exception: IllegalArgumentException: Illegal character in query at index 153.
Position 153 equates to the first space character.
It would seem that the {sms_text} variable is not being URL encoded before being replaced in the URL string for the HTTP request. I would think that this would happen with any variable.
For the moment I can achieve what I need to via an email action, but this issue needs to be addressed.
Thanks,
Pete
Just getting into this really cool tool, but have found what I believe to be a bug.
I created a simple flow to forward any received SMS to Prowl using an HTTP request action. While testing I was only using the word "test" (no quotes) but when I sent a text more than one word in, e.g. "This is a test", the flow errors.
Examining the log reveals an exception: IllegalArgumentException: Illegal character in query at index 153.
Position 153 equates to the first space character.
It would seem that the {sms_text} variable is not being URL encoded before being replaced in the URL string for the HTTP request. I would think that this would happen with any variable.
For the moment I can achieve what I need to via an email action, but this issue needs to be addressed.
Thanks,
Pete