Plus sign doesnt get through to bot
Plus signs in chat text don't travel to the bot, but are replaced by blank space. I've pattern-matched text the bot receives, the plus sign is lost on its way to the bot.
Chat client is google mail chat widget. Botname is doct4mytest. Thanks for your great service!
Comments are currently closed for this discussion. You can start a new one.
2 Posted by System on 11 Jun, 2009 03:36 PM
A Lighthouse ticket was created for this discussion
3 Posted by Anthony Webb on 11 Jun, 2009 03:36 PM
Thanks man, we're on it.
Anthony Webb closed this discussion on 11 Jun, 2009 03:36 PM.
Doc-T re-opened this discussion on 11 Jun, 2009 03:46 PM
4 Posted by Doc-T on 11 Jun, 2009 03:46 PM
Whooah, that was a fast reply!
Also, backslashes get DOUBLED, but I haven't checked, where this happens.
5 Posted by System on 11 Jun, 2009 05:40 PM
This discussion was assigned to ticket 35.
6 Posted by mpahic on 12 Jun, 2009 12:14 PM
I thought this was a php issue, not a bot issue.
7 Posted by Doc-T on 12 Jun, 2009 01:50 PM
If I send the text %2B to the bot, it is received as a plus sign. So this appears to be an escaping issue.
As the text is moved from the imified platform via http/post to the bot, I'd assume that the call to the bot by the imified platform would include an appropriate encoding of the text string to the bot, so that the receiving end (here, the php runtime) can decode the encapsulated url string to receive the actual message.
If I read http://en.wikipedia.org/wiki/Percent-encoding and the linked RFC correctly, a plus sign and various other characters must be percent-encoded before being sent along. Apparantly php sticks to this and decodes the post parameters before passing them into the global variables.
Would be interesting to know, if the plus sign reaches the imified platform in the first instance, before it is sent along to the bot, or if the imified platform correctly encodes a string already received in an incorrect format from the chat application.
8 Posted by Anthony Webb on 13 Jun, 2009 03:31 PM
I think we've fixed this issue, look for the fix in our release later tonight.
Anthony Webb closed this discussion on 13 Jun, 2009 03:31 PM.