URI::InvalidURIError #488

koko37 · 2013-08-13T14:35:47Z

Hello Everybody!

I am trying to build SOAP client, and installed Savon 2.3.0 in gemfile.
And wrote test code, like below.
But while in running, there is an error "URI::InvalidURIError".

Please help me if possible.
Thanks.

def test
    client = Savon.client do
      wsdl "https://api.propertyware.com/pw/services/PWServices?wsdl"
      endpoint "https://api.propertyware.com/pw/services/PWServices"
      namespace "https://api.propertyware.com/pw/services/PWServices"
    end

    response = client.call(:get_contacts_by_name, message: {first_name: "foo" ,last_name: "foo"})
  end

rubiii · 2013-08-26T10:23:08Z

tried your code without modifications usng savon 2.3.0 and it's working fine.
are you running this in a test environment? can you try running it "standalone"?

koko37 · 2013-08-28T01:37:20Z

I resolved this issue by installing gem 'httpclient'.
thanks.

codebender · 2013-09-14T21:03:16Z

what's the cause of this error? I got it as well after upgrading to 2.3 version of the savon gem. installing gem 'httpclient' also fixed the error...

bradly-swart · 2013-09-25T04:00:04Z

Thanks, this helped fix my error too.

I changed to another version of ruby using rbenv, re-installed the savon gem, ran 'rbenv rehash'.
After install the 'httpclient' gem things started working again...well mostly except for the 302 HTTPError I'm getting now.

johnagan · 2013-09-29T16:40:41Z

That was an hour of my life I'll never get back :)

Worked for me too! thx

elsurudo · 2013-10-03T18:21:26Z

Had the same issue. This should probably be documented somewhere. Thanks!

codebender · 2014-01-09T23:48:01Z

pretty please, document this.

tjarratt · 2014-01-10T02:05:33Z

@MisterBender did you ever discover the root cause of this error? I'll gladly document it, but it would be nice to know what is causing this error in the first place.

marekstachura · 2014-01-20T22:15:52Z

Hi,

same here, I'm using latest version 2 (v 2.3.3) of the gem and latest Ruby 1.9.3 (1.9.3-p484).
When I call:

client = Savon.client(wsdl: 'https://ec.europa.eu/taxation_customs/vies/checkVatService.wsdl')

I'm getting following exception:

/Users/marek/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/1.9.1/uri/common.rb:176:in `split': bad URI(is not URI?): {:host=>"ec.europa.eu", :path=>"/taxation_customs/vies/checkVatService.wsdl", :port=>"80", :query=>nil, :scheme=>"http", :headers=>{}, :body=>nil, :ssl_verify_peer=>true} (URI::InvalidURIError)
from /Users/marek/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/1.9.1/uri/common.rb:211:in `parse'
from /Users/marek/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/1.9.1/uri/common.rb:747:in `parse'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/excon-0.9.6/lib/excon/connection.rb:20:in `initialize'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/httpi-2.1.0/lib/httpi/adapter/excon.rb:17:in `new'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/httpi-2.1.0/lib/httpi/adapter/excon.rb:17:in `initialize'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/httpi-2.1.0/lib/httpi.rb:192:in `new'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/httpi-2.1.0/lib/httpi.rb:192:in `load_adapter'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/httpi-2.1.0/lib/httpi.rb:135:in `request'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/httpi-2.1.0/lib/httpi.rb:106:in `get'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/wasabi-3.2.3/lib/wasabi/resolver.rb:42:in `load_from_remote'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/wasabi-3.2.3/lib/wasabi/resolver.rb:32:in `resolve'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/wasabi-3.2.3/lib/wasabi/document.rb:141:in `xml'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/wasabi-3.2.3/lib/wasabi/document.rb:159:in `parse'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/wasabi-3.2.3/lib/wasabi/document.rb:146:in `parser'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/wasabi-3.2.3/lib/wasabi/document.rb:63:in `soap_actions'
from /Users/marek/.rvm/gems/ruby-1.9.3-p484/gems/savon-2.3.3/lib/savon/client.rb:28:in `operations'
from vies.rb:4:in `<main>'

After installing the gem httpclient it works again.
Thanks.

catskull · 2014-05-08T18:32:37Z

Bump for this.

That was an hour of my life I'll never get back

tjarratt · 2014-05-09T06:03:15Z

I feel like I'm kind of letting everyone down, because it's pretty clear this is a real issue that has affected a lot of people now, but I still haven't been able to reproduce this.

Gemfile

source :rubygems
gem "savon", "~> 2.3.3"

rvm use ruby-1.9.3@savon-test --create
bundle
bundle exec rib
irb(main):001:0> RUBY_VERSION
=> "1.9.3"
irb(main):002:0> require 'savon'; Savon::VERSION
=> "2.3.3"
irb(main):003:0> Savon.client(wsdl: 'https://ec.europa.eu/taxation_customs/vies/checkVatService.wsdl').operations

No exceptions. The backtrace that @marekstachura posted mentioned Excon as the adapter, so it makes some sense that adding HTTPClient might fix this, because it changes the http adapter Savon uses, and the URI generated goes through a separate path.

However, the version of Excon in the trace is 0.9.6 which was released on 02/22/12, so... it would be somewhat surprising if that worked without any bugs.

@catskull -- since you were the last person to encounter this, could you tell me which http adapter you're using, and which version if it is in your Gemfile.lock ?

jonathan-mui · 2014-06-05T23:16:11Z

I experienced this issue with an existing app today. After adding gem 'httpclient' I no longer saw the issue. Removing the gem after brought the issue back, so for my app it was definitely the culprit. However, I tried to create a minimalist case with a new rails app and same ruby and gem versions, but could not reproduce the issue. My stack trace is similar. How do I find out which http adapter I'm using?

URI::InvalidURIError: bad URI(is not URI?): {:host=>"secure.echosign.com", :path=>"/services/EchoSignDocumentService18", :port=>"443", :query=>"wsdl", :scheme=>"https", :headers=>{}, :body=>nil, :ssl_verify_peer=>true}
    from /Users/<user>/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/uri/common.rb:176:in `split'
    from /Users/<user>/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/uri/common.rb:211:in `parse'
    from /Users/<user>/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/uri/common.rb:747:in `parse'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/excon-0.16.10/lib/excon/connection.rb:20:in `initialize'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/httpi-2.1.0/lib/httpi/adapter/excon.rb:17:in `new'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/httpi-2.1.0/lib/httpi/adapter/excon.rb:17:in `initialize'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/httpi-2.1.0/lib/httpi.rb:192:in `new'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/httpi-2.1.0/lib/httpi.rb:192:in `load_adapter'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/httpi-2.1.0/lib/httpi.rb:135:in `request'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/httpi-2.1.0/lib/httpi.rb:106:in `get'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/wasabi-3.2.3/lib/wasabi/resolver.rb:42:in `load_from_remote'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/wasabi-3.2.3/lib/wasabi/resolver.rb:32:in `resolve'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/wasabi-3.2.3/lib/wasabi/document.rb:141:in `xml'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/wasabi-3.2.3/lib/wasabi/document.rb:159:in `parse'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/wasabi-3.2.3/lib/wasabi/document.rb:146:in `parser'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/wasabi-3.2.3/lib/wasabi/document.rb:63:in `soap_actions'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/savon-2.3.3/lib/savon/client.rb:28:in `operations'
    from (irb):5
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/railties-3.2.18/lib/rails/commands/console.rb:47:in `start'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/railties-3.2.18/lib/rails/commands/console.rb:8:in `start'
    from /Users/<user>/.rvm/gems/ruby-2.1.1@<gemset>/gems/railties-3.2.18/lib/rails/commands.rb:41:in `<top (required)>'
    from script/rails:6:in `require'
    from script/rails:6:in `<main>'

tjarratt · 2014-06-12T20:41:07Z

@jonathan-mui the current adapter can be found on the HTTPI namespace.

HTTPI::Adapter.use # :httpclient by default

There's an order that HTTPI attempts to load them in...

    LOAD_ORDER = [:httpclient, :curb, :em_http, :excon, :net_http, :net_http_persistent]

jonathan-mui · 2014-06-12T20:48:34Z

Without the httpclient gem, the adapter used is :excon

catskull · 2014-06-17T22:49:44Z

@tjarratt I installed httpclient, which installed httpclient (2.3.4.1). Also noted that I'm using Rails 3.2.11. Not sure which version of rails you're using for testing, but that could be something to start with.

I also blogged about it here.

Not trying to nerd rage too hard, your gem has been super helpful. Just a heads up in the readme or something would be nice.

tjarratt · 2014-06-18T06:36:41Z

Might be a good idea to link to this issue from your blog post @catskull. I really thought that the "will not do anything" part was going to link here :)

Writing a good README is tough. I think there's a pretty good argument to be made for a FAQ, or maybe a wiki to document some of these challenges people have with Savon. Thoughts?

Honestly, when I have problems like this (which is basically every single day of my life 💣) I end up spending a lot of time searching for very specific error messages on google, which almost always links me to a Stack Overflow or Github page with some pretty helpful discussion that helps direct me to what I need to change.

tjarratt · 2014-06-18T06:37:31Z

Maybe I'm coming at this from the wrong direction. What if we put a hard dependency on httpclient in Savon, to help minimize these problems? It seems like that works 99% of the time for everyone...

catskull · 2014-06-18T17:04:14Z

Good point, I will update my blog to point here.

I really think that all you'd need to do is update the README to read something like:

Savon version 2 is available through Rubygems and can be installed via:
$ gem install savon
or add it to your Gemfile like this:
gem 'savon', '~> 2.3.0'

Some users have reported an error reading URI::InvalidURIError. If you see this as well, a solution is installing httpclient:
$ gem install httpclient
or add it to your Gemfile:
gem 'httpclient'

Otherwise, a hard dependency may make sense, but I squirm thinking that there may be that one person out there that doesn't need it. I guess at the end of the day, it's not really a big deal to have a dependency.

As for your problem solving (:bomb:) skills, that's essentially what I did, which led me here. And that's kind of what I mean when I quoted

That was an hour of my life I'll never get back

because it seemed like such a small issue with a really easy fix. We should all spend that time researching things that don't have straightforward/easy solutions! 😄

tjarratt · 2014-07-01T05:38:38Z

Cool, updating the README to include a small FAQ. Will try adding to that as I see more patterns in community issues evolve.

@catskull

Sparked by the always helpful @catskull on this issue: #488 (comment)

codebender · 2014-07-02T22:00:17Z

👍

Bodata · 2017-05-11T13:20:17Z

Hi,
installed savon-2.11.1 on an older linux system, ruby 1.9x
I had the same error, after a gem install httpclient the problem was solved.

tjarratt · 2017-05-11T18:29:58Z

@Bodata just a friendly reminder that Ruby 1.9 was considered "end of life" over two years ago and no longer receives bug fixes or security updates. You should upgrade to a modern ruby!!! https://www.ruby-lang.org/en/news/2014/01/10/ruby-1-9-3-will-end-on-2015/ Sent From A Very Small Keyboard

…

Le 11 mai 2017 à 15:20, Bodata ***@***.***> a écrit : Hi, installed savon-2.11.1 on an older linux system, ruby 1.9x I had the same error, after a gem install httpclient the problem was solved. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

koko37 closed this as completed Aug 28, 2013

tjarratt added a commit that referenced this issue Jul 1, 2014

Add a FAQ to discuss URI::InvalidURIError httpi issue

d3027b0

Sparked by the always helpful @catskull on this issue: #488 (comment)

This was referenced Jul 29, 2015

Installing Twitter Gem breaks Savon due to HTTPI LOAD_ORDER preferring http over net_http savonrb/httpi#156

Closed

Loosen savon's dependency upon HTTPi LOAD_ORDER. This causes issues on many levels #710

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

URI::InvalidURIError #488

URI::InvalidURIError #488

koko37 commented Aug 13, 2013

rubiii commented Aug 26, 2013

koko37 commented Aug 28, 2013

codebender commented Sep 14, 2013

bradly-swart commented Sep 25, 2013

johnagan commented Sep 29, 2013

elsurudo commented Oct 3, 2013

codebender commented Jan 9, 2014

tjarratt commented Jan 10, 2014

marekstachura commented Jan 20, 2014

catskull commented May 8, 2014

tjarratt commented May 9, 2014

jonathan-mui commented Jun 5, 2014

tjarratt commented Jun 12, 2014

jonathan-mui commented Jun 12, 2014

catskull commented Jun 17, 2014

tjarratt commented Jun 18, 2014

tjarratt commented Jun 18, 2014

catskull commented Jun 18, 2014

tjarratt commented Jul 1, 2014

codebender commented Jul 2, 2014

Bodata commented May 11, 2017

tjarratt commented May 11, 2017 via email

URI::InvalidURIError #488

URI::InvalidURIError #488

Comments

koko37 commented Aug 13, 2013

rubiii commented Aug 26, 2013

koko37 commented Aug 28, 2013

codebender commented Sep 14, 2013

bradly-swart commented Sep 25, 2013

johnagan commented Sep 29, 2013

elsurudo commented Oct 3, 2013

codebender commented Jan 9, 2014

tjarratt commented Jan 10, 2014

marekstachura commented Jan 20, 2014

catskull commented May 8, 2014

tjarratt commented May 9, 2014

jonathan-mui commented Jun 5, 2014

tjarratt commented Jun 12, 2014

jonathan-mui commented Jun 12, 2014

catskull commented Jun 17, 2014

tjarratt commented Jun 18, 2014

tjarratt commented Jun 18, 2014

catskull commented Jun 18, 2014

tjarratt commented Jul 1, 2014

codebender commented Jul 2, 2014

Bodata commented May 11, 2017

tjarratt commented May 11, 2017 via email