#3
Post
by Martinus » 16 Jan 2017, 09:34
It seems that if ¶ is shown somewhere in a webform, the ¶ is interpreted as the HTML escape sequence for a paragraph sign, looking like a backwards P.
I don't know where it should be fixed and it's possible that it does not occur on all browsers.
But there's a workaround for this particular bug: Use the ¶m as the first name-value pair in the URL so it becomes ?param and it will no longer be misinterpreted.
Example:
change this:
sendtohttp 192.168.0.8,8080,/json.htm?type=command¶m=udevice&idx=286&svalue=%eventvalue%
into:
sendtohttp 192.168.0.8,8080,/json.htm?param=udevice&type=command&idx=286&svalue=%eventvalue%
So we've just changed the order in which the url is build up.