OAuth.Net.Compants.HMacSha1SigningProvider.CheckSignature intermittently incorrectly returns false due to '+' vs ' ' encoding issue

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Set a breakpoint on the return line of the
OAuth.Net.Compants.HMacSha1SigningProvider.CheckSignature method
2. Hit the "Echo service provider" example and click the "Getting an access
token" link.
3. If the signature contains a space, you will see the expectedSignature
and actualSignature values differ only by the encoding of the space. (NOTE:
if the signature doesn't contain a space, go back to step 2, refresh it to
generate new oauth params and repeat)

Original issue reported on code.google.com by jaysen.m...@gmail.com on 18 Aug 2009 at 11:27

[GoogleCodeExporter]

The issue was in the way the URL was being written out on the echo service 
provider
web page.  The + character wasn't a space but a + value.  Because this wasn't 
being
encoded when written out, when followed IIS was de-coding the + value into a 
space
incorrectly.

A change has been made to the trunk.

Original comment by chris.s....@gmail.com on 3 Sep 2009 at 2:23

• Changed state: Fixed