Re: [Chicken-users] Re: fatal bug in xml-rpc

[Daishi Kato]

Sure.

The following is the network dump of the request and response:

T 127.0.0.1:43241 -> 127.0.0.1:60234 [AP]
 POST /RPC2 HTTP/1.1..Content-Type: text/xml..User-Agent: Apache XML RPC 3.0
  (Sun HTTP Transport)..Content-Length: 299..Cache-Control: no-cache..Pragma
 : no-cache..Host: localhost:60234..Accept: text/html, image/gif, image/jpeg
 , *; q=.2, */*; q=.2..Connection: keep-alive....
#
T 127.0.0.1:43241 -> 127.0.0.1:60234 [AP]
 <?xml version="1.0" encoding="UTF-8"?><methodCall><methodName>get</methodNa
 me><params><param><value><base64>0QIVHz4imX4EF4A+sGS2C0nq3lg=</base64></val
 ue></param><param><value><i4>10</i4></value></param><param><value><base64/>
 </value></param><param><value>get.py</value></param></params></methodCall>
##
T 127.0.0.1:60234 -> 127.0.0.1:43241 [AP]
 HTTP/1.1
##
T 127.0.0.1:60234 -> 127.0.0.1:43241 [AP]
  200 OK..Server: spiffy No. 2 (Release 37) on Chicken 2.5..Location: raccoo
 n..Content-type: text/xml..Content-length: 310....<?xml version="1.0"?>.<me
 thodResponse>. <fault>.  <value>.   <struct>.    <member>.     <name>faultC
 ode</name><value><int>1</int></value>.    </member>.    <member>.     <name
 >faultString</name><value><string>invalid rpc format</string></value>.    <
 /member>.   </struct>.  </value>. </fault>.</methodResponse>


On 12/5/06, felix winkelmann <address@hidden> wrote:
> On 12/5/06, Daishi Kato <address@hidden> wrote:
> > No, it still says "invalid rpc format".
> >
>
> Can you send me the XML reply text?
>
>
> cheers,
> felix
>
>
> --
> http://galinha.ucpel.tche.br:8081/blog/blog.ssp