Kevin Killingsworth

I just tried this out, and I'm afraid it hasn't helped fix the problem. Here's the code in question, and it appears to be still intact: https://github.com/WP-API/OAuth1/blob/141f4f80d260ed9c2acb10687b2dc0e136fea4c7/lib/class-wp-rest-oauth1.php#L733 ``` php protected...

From my Client: ``` String to sign: "GET&http%3A%2F%2Fvagrant.local%2Foauth1%2Frequest&oauth_callback%3Dhttp%253A%252F%252Flocalhost%253A8080%252Fredirect.html%253Fproxy_url%253Dhttp%25253A%25252F%25252Flocalhost%25253A8080%25252F%2526state%253D%25257B%252522client_id%252522%25253A%252522ke3cgrDMqOXq%252522%25252C%252522network%252522%25253A%252522wpApi%252522%25252C%252522display%252522%25253A%252522popup%252522%25252C%252522callback%252522%25253A%252522_hellojs_3u0c4lde%252522%25252C%252522state%252522%25253A%252522%252522%25252C%252522redirect_uri%252522%25253A%252522http%25253A%25252F%25252Flocalhost%25253A8080%25252Fredirect.html%252522%25252C%252522scope%252522%25253A%252522basic%252522%25252C%252522oauth%252522%25253A%25257B%252522version%252522%25253A%2525221.0a%252522%25252C%252522auth%252522%25253A%252522http%25253A%25252F%25252Fvagrant.local%25252Foauth1%25252Fauthorize%252522%25252C%252522request%252522%25253A%252522http%25253A%25252F%25252Fvagrant.local%25252Foauth1%25252Frequest%252522%25252C%252522token%252522%25253A%252522http%25253A%25252F%25252Fvagrant.local%25252Foauth1%25252Faccess%252522%25257D%25252C%252522oauth_proxy%252522%25253A%252522http%25253A%25252F%25252Flocalhost%25253A8080%25252Foauthproxy%252522%25257D%2526client_id%253Dke3cgrDMqOXq%26oauth_consumer_key%3Dke3cgrDMqOXq%26oauth_nonce%3D3765a3ae273396000%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1449476002%26oauth_version%3D1.0" ``` From the Server (OAuth1 plugin): ``` [07-Dec-2015 08:13:23 UTC] $string_to_sign="GET&http%3A%2F%2Fvagrant.local%2Foauth1%2Frequest&oauth_callback%3Dhttp%253A%252F%252Flocalhost%253A8080%252Fredirect.html%253Fproxy_url%253Dhttp%253A%252F%252Flocalhost%253A8080%252F%2526state%253D%257B%2522client_id%2522%253A%2522ke3cgrDMqOXq%2522%252C%2522network%2522%253A%2522wpApi%2522%252C%2522display%2522%253A%2522popup%2522%252C%2522callback%2522%253A%2522_hellojs_3u0c4lde%2522%252C%2522state%2522%253A%2522%2522%252C%2522redirect_uri%2522%253A%2522http%253A%252F%252Flocalhost%253A8080%252Fredirect.html%2522%252C%2522scope%2522%253A%2522basic%2522%252C%2522oauth%2522%253A%257B%2522version%2522%253A%25221.0a%2522%252C%2522auth%2522%253A%2522http%253A%252F%252Fvagrant.local%252Foauth1%252Fauthorize%2522%252C%2522request%2522%253A%2522http%253A%252F%252Fvagrant.local%252Foauth1%252Frequest%2522%252C%2522token%2522%253A%2522http%253A%252F%252Fvagrant.local%252Foauth1%252Faccess%2522%257D%252C%2522oauth_proxy%2522%253A%2522http%253A%252F%252Flocalhost%253A8080%252Foauthproxy%2522%257D%2526client_id%253Dke3cgrDMqOXq%26oauth_consumer_key%3Dke3cgrDMqOXq%26oauth_nonce%3D3765a3ae273396000%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1449476002%26oauth_version%3D1.0" ```

@rmccue It's been a while since we last had activity here. Is this still something you'd like to address?

In my case, normalize_parameters() is really messing up my already partially encoded parameters, so by removing normalize_parameters() instead, I was able to keep the rawurldecode() calls. See: #91 @sblaz ,...

In my case, normalize_parameters() is really messing up my already partially encoded parameters, so by removing normalize_parameters() instead, I was able to keep the rawurldecode() calls. See: #91 I have...