I have an OAuth::AccessToken that is able to get(url). But when I do

RestClient.add_before_execution_proc do |req, params|
@access_token.sign!(req)
end
...
RestClient.get(url)

I get back 401, oauth_problem=signature_invalid.

Ruby 1.9.2p180, rest-client 1.6.1, also tried master from github.

Le 4 mai 2011 à 05:36, Brian Lewis a écrit :

I have an OAuth::AccessToken that is able to get(url). But when I do

RestClient.add_before_execution_proc do |req, params|
@access_token.sign!(req)
end
...
RestClient.get(url)

I get back 401, oauth_problem=signature_invalid.

Ruby 1.9.2p180, rest-client 1.6.1, also tried master from github.

Perhaps a change in the oauth gem code, I didn't used it since a long time
From their API could you try

RestClient.add_before_execution_proc do |req, params|
req.oauth! (@consumer, @access_token)
end

and tell me if it works ?



Regards

A.

On Friday, 06.05.11 at 16:20, Archiloque wrote:

From their API could you try
RestClient.add_before_execution_proc do |req, params|
req.oauth! (@consumer, @access_token)
end

I get #<NoMethodError: undefined method `address' for #<OAuth::Consumer:0x99b072c>>

On Friday, 06.05.11 at 12:48, Nicholas Wieland wrote:

If you're using the Rails plugin you have to patch it.
http://groups.google.com/group/oauth-ruby/browse_thread/thread/6b2bb480255afaf1

Hi, thanks. Could you elaborate on this? I thought I understood what to
patch, but I don't see any verify_request method in either oauth or
rest-client.

On May 6, 2011, at 1:12 PM, Brian Lewis wrote:

On Friday, 06.05.11 at 12:48, Nicholas Wieland wrote:

If you're using the Rails plugin you have to patch it.
http://groups.google.com/group/oauth-ruby/browse_thread/thread/6b2bb480255afaf1

Hi, thanks. Could you elaborate on this? I thought I understood what to
patch, but I don't see any verify_request method in either oauth or
rest-client.

The rails plugin, not rest_client and not oauth.
If you're not using the rails plugin, I don't know.

ngw

The error was the result of bad documentation (not rest-client's!) about
what URLs to use. The error went away after changing the consumer URL.
Thank you, sorry for the noise.