You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is almost certainly deliberate behaviour but I'd just like to know how to work around this:
I've got an encrypted string being passed as a param when calling a hub method from my js.
When using the alpha this worked just fine. With the RC the string isn't being escaped (so plus signs appear to be converted to spaces) which obviously causes issues with the decryption.
Oh that's great, like someone else said, very efficient!
Sorry missed that issue when I looked for it..
I guess I'm going to have to go back to the alpha version for the demo tomorrow. Doubt you'll release this before then! Do you have a schedule for the next release?
This is almost certainly deliberate behaviour but I'd just like to know how to work around this:
I've got an encrypted string being passed as a param when calling a hub method from my js.
When using the alpha this worked just fine. With the RC the string isn't being escaped (so plus signs appear to be converted to spaces) which obviously causes issues with the decryption.
Here's an example of the encrypted string:
tfL2tUFP5tbNxz0bBJFJHcIJOZV3zcj2ebyvIs7n/4blHrLCPRWbQ16d5h1GKuC0mOEhgiWZoi44HN9JCuB4HFudHjey1jLphaKDW0kl+wmR9tsutKhxthejRb1nhTKAcXGHHfI4cgXVOLbnUuihAOwK3q00vK2heNDWJ8DEWHQ=JkeukSmux1fdF5RdknlLr3WIjufiv1L2BSaWGkQaFajcg1MUKSaBfy43xeVxH5puR6DAOTcY6QmeD6N0x8KxeT5D3Gfq/WvMxukhEuJ4DWRleeU1sGYyaX6IsWfR8bm99+5YaB6Iz0Q/XdhA+QhLiIgo7gePAGPXhUzcfEDmwBA=
Here's what ends up in the server-side hub method:
tfL2tUFP5tbNxz0bBJFJHcIJOZV3zcj2ebyvIs7n/4blHrLCPRWbQ16d5h1GKuC0mOEhgiWZoi44HN9JCuB4HFudHjey1jLphaKDW0kl wmR9tsutKhxthejRb1nhTKAcXGHHfI4cgXVOLbnUuihAOwK3q00vK2heNDWJ8DEWHQ=JkeukSmux1fdF5RdknlLr3WIjufiv1L2BSaWGkQaFajcg1MUKSaBfy43xeVxH5puR6DAOTcY6QmeD6N0x8KxeT5D3Gfq/WvMxukhEuJ4DWRleeU1sGYyaX6IsWfR8bm99 5YaB6Iz0Q/XdhA QhLiIgo7gePAGPXhUzcfEDmwBA=
Assuming this behaviour is deliberate then how would I work around this? If it's not it could be related to issue 94 which is now closed.
The text was updated successfully, but these errors were encountered: