What steps will reproduce the problem?
1. Try to sign a url using osapiSecurityToken and a hi5 token with special
characters like space
2. Get a url
3. Check url against RFC-1738.
What is the expected output? What do you see instead?
Url should be valid
What version of the product are you using? On what operating system?
v1.1.0
Please provide any additional information below.
Need to urlencode the security token before creating the url. I have
attached a patch.
Original issue reported on code.google.com by sma...@gmail.com on 2 Nov 2009 at 8:18
Original issue reported on code.google.com by
sma...@gmail.com
on 2 Nov 2009 at 8:18Attachments: