I still can do this web service right so I ask for some help please.
I got the wsdl and make a client with wsdl2ruby.rb. When I run ruby -d
client I got the following output:
= Request
! CONNECT TO XXX.XXX.XXX.XXX:80
! CONNECTION ESTABLISHED
POST /DataFeed/DataFeed.asmx HTTP/1.1
SOAPAction: “Bing”
Content-Type: text/xml; charset=utf-8
User-Agent: SOAP4R/1.5.5 (http-access2.rb/1.1.1.1, ruby 1.8.5
(2006-12-25) [i386
-mswin32])
Date: Mon Feb 19 20:41:00 +0100 2007
Content-Length: 339
Host: XXX.XXX.XXX.XXX
Content-Type: text/xml; charset=utf-8
xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
Server: Microsoft-IIS/5.0
ruby. I ask you for some help, example or a hint.
Thanks in advance.
dima
Just a guess (knowing almost nothing about IIS, NTLM nor WSDL): This
seems to be an authentication problem. Somewhere (ruby’s tracker?
svn?) there’s a patch that adds ntlm auth support for net/http.
Perhaps you could try that. (see ruby-core:10341)
Your web server is rejecting your connection attempt, because you
haven’t authenticated. If your client will only run on Windows
systems, you could try the patch below[1], which supports NTLM
authentication; otherwise, consider using client IP address, or some
application-level control, for authentication, as NTLM is a
proprietary Microsoft auth mechanism, and will block most client
platforms from being able to access your service.
Thank you for you swift response.
I guessed that the problem is with authentication and with NTLM.
Unfortunately I do not know what that is all about.
It will be extremely helpful if you have some kind of sample code.
I had to use the 3rd party web service that will not change by mine
request.
The rubyntlm has a working http example, throughout socket connection,
that I will explore and try to combine with soap4r.
I will share the results of this quest.
Thank you for you swift response.
I guessed that the problem is with authentication and with NTLM.
Unfortunately I do not know what that is all about.
It will be extremely helpful if you have some kind of sample code.
My suggestion would be to talk to your server administrator, and see
about turning off the NTLM auth – as I said, it’s a proprietary spec
used almost exclusively Microsoft-only shops, and is going to cause
you all kinds of problems when trying to access your web service from
other client platforms. (Plus, anything based on NTLM auth is
inherently insecure, as it’s rather easy to crack the LanMan hash
format.)
If you really need HTTP authentication, stick to the basics: HTTP-
Digest, optionally protected by HTTPS if you need transport-level
encryption, too. Take a look here for some examples of using standard
HTTP authentication with a ruby SOAP client:
Hope that helps,
-rcoder
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.