OAuth1 - Path Segments with Special Char "!" - Results in Auth Error about restsharp HOT 3 OPEN

There was a change released in v111 to handle special characters differently. However, the test that checks the encoding according to RFC 3986 is failing now.

It would be good to add expected and actual signature strings in OAuth1 issues, otherwise it turns to a guess game.

from restsharp.

@alexeyzimarev
Thank you, V111.2.0 resolved the issue.
Through testing, it works if you put the special character directly in the URL now too (no need to put it into a URL Segment).

Here are the signature strings requested:

Successful REST Req with V111.2.0:
oauth_signature=""p97P4FkwbKkvLI5AirFV5Flgb%2BcdsdGUWnSg2d3zQeo%3D""

Unsuccessful REST Req with V110.2.0
oauth_signature=""w5UmuCZysIV4GvDNxMfwXQMbQ5z%2FIFZm1xR7vQ9shQE%3D""

However, I am not sure how useful these are to you without the OAuth credentials used to generate these signatures.

If you have any suggestions on how I could help further, I would be more than happy to help and provide additional info for your unit tests.

from restsharp.

You don't have to provide real credentials. If you look at the tests I added, I used fixed values from Twitter OAuth1 docs that specifies values for everything, then it shows how the signature base will look like, and what the resulting signature will be. That page in their docs allowed me to create a reliable set of tests to verify that the code generates the correct signature base, and the actual signature is correct.

Could you please write a comment if there's any remaining issue now with the latest version? If yes, it'd be nice to have a repro code.

from restsharp.