Uh oh!
There was an error while loading. Please reload this page.
Fix for #231 Support for LinkedIn Field-Selector Notation - #250
Conversation
Fixes the broken .NET RFC 3986 encoding for Uri.EscapeDataString
devatwork
commented
May 8, 2012
I just added a test for this fix. Let me know if there is something wrong with the code. |
ayoung
commented
May 9, 2012
Just pulled this in. Thanks. I had to modify this a bit to be compatible with Windows Phone. It doesn't have the Uri.HexEscape method so I just hard coded a hex map. |
devatwork
commented
May 9, 2012
Hi Andrew, thanks for pulling the change in. I am installing the Windows Phone SDK now to make sure future pull requests do work on Windows Phone. |
ayoung
commented
May 9, 2012
new version on nuget coming soon. On Wednesday, May 9, 2012 at 0:19, Bert Willems wrote:
|
Fixes the broken .NET RFC 3986 encoding for Uri.EscapeDataString, which causes the LinkedIN field selector signature generation bug.
See the following stackoverflow question about the implementation details of this fix.
http://stackoverflow.com/questions/846487/how-to-get-uri-escapedatastring-to-comply-with-rfc-3986.
I ran all the units and my own LinkedIN tests with this fix succesfully.