Not adding the leading slash leads to an anonymous NoMethodError: undefined method `downcase' for nil:NilClass

[ferdi2005]

Not adding the traling slash in the OAuth consumer leads to an uneasily debuggable NoMethodError: undefined method 'downcase' for nil:NilClass

Example, using:
oauth_consumer = OAuth::Consumer.new(ENV["CONSUMER_KEY"], ENV["CONSUMER_SECRET"], :site => "https://commons.wikimedia.org", :request_token_path => "w/index.php?title=Special:OAuth/initiate", :authorize_path => "wiki/Special:OAuth/authorize", :access_token_path => "wiki/Special:OAuth/token",)

instead of:

oauth_consumer = OAuth::Consumer.new(ENV["CONSUMER_KEY"], ENV["CONSUMER_SECRET"], :site => "https://commons.wikimedia.org", :request_token_path => "/w/index.php?title=Special:OAuth/initiate", :authorize_path => "/wiki/Special:OAuth/authorize", :access_token_path => "/wiki/Special:OAuth/token",)

leads to a NoMethodError: undefined method 'downcase' for nil:NilClass and not to a clearer error.

[cyrillefr]

Hello, been through this problem too.

When playing with auth with the Twitter API:
access_token.get('/2/users/117345550/tweets') -> OK
access_token.get('2/users/117345550/tweets') -> KO (note there is no / at pos 0).

The problem lies in the lib/oauth/consumer.rb file:

def request(http_method, path, token = nil, request_options = {}, *arguments)
   if path !~ /^\//
     @http = create_http(path) # we go here if no leading slash

Which leads us to (same file):

def create_http(_url = nil) 
  . . .
  if _url.nil? || _url[0] =~ /^\//
    our_uri = URI.parse(site)
  else
    our_uri = URI.parse(_url) # we are here since url[0] is not a "/"
  end

So, instead of parsing something like api.twitter.com (the host), we parse a path (2/users/etc)
The resulting http object has a host attribute of nil

All the way down, we hit (file request_proxy/base.rb)

def normalized_uri
  "#{u.scheme.downcase}://#{u.host.downcase} # since u.host is nil, raise Error

I am not sure why, we would parse a path if it does not begin with a slash.
But the fix would be within these methods.

[pboling]

Thanks for the report @ferdi2005 , and the analysis @cyrillefr . I'll work on fixing this issue for the next release, which will be at least a minor bump.