From: yermej <yermej@...>
Date: 2008-07-08T22:56:20+09:00
Subject: Re: XMLRPC Question

On Jul 7, 5:09 pm, Michael Taras <michaelta...@gmail.com> wrote:

> Just from my research, it seems that the error is popping up because the
> code is trying to match the xml definition line to an HTTP response
> code, which of course is not working.  My guess is that the server is
> not returning any sort of http status, and just the xml, but I'm really
> not sure.  This is my first time messing with any xmlrpc stuff.

That seems to be the case - XMLRPC uses HTTP for transport so a
request should be an HTTP POST and a response should have an HTTP
status and HTTP headers (which must include Content-Length and Content-
Type - there can be others too).

> But
> if it is something wrong on their end then I can probably get that
> fixed, I guess I just need to know exactly what is wrong.

As it stands, they haven't correctly implemented the XMLRPC spec.
Point them here http://www.xmlrpc.com/spec for the actual spec. It's
really simple and shouldn't be much work to implement - there's
probably a library in whatever language/environment they're using. As
for specifics, the response isn't a valid HTTP response - they need to
have something like:

HTTP/1.1 200 OK
Content-Length: 32
Content-Type: text/xml

<?xml version="1.0"?>
<methodResponse>
  <params>
    <param>
      ...
</methodResponse>

A valid request would be something like (the headers shown are
required):

POST / HTTP/1.0
User-Agent: whatever/1.1
Host: you.must.have.this.tld
Content-Type: text/xml
Content-Length: 32

<?xml version="1.0"?>
<methodCall>
  <methodName>ping</methodName>
  <params>
  <param>
  ...
</methodCall>

Did you really have to type all that to test the function? If not, it
may be easier to just use some sort of Ruby telnet package and adapt
your app to their odd format. Just depends on what the other side is
willing to do.