Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#27 http problems?

open
nobody
None
5
2001-11-08
2001-11-08
Eric Kamm
No

I've had great success using the client class
making RPCs to Zope and Python XMLRPC servers.

When I have tried to make RPCs to IIS servers,
I have problems. Here's a client log from calling
a simple 'hello world' function:

11/08/2001 11:01:54 <source 192.9.200.225:80> client
queueing command ('helloWorld', ('eric',))
11/08/2001 11:01:54 <source 192.9.200.225:80> client
request is 'POST /Stuff/xmlrpc/serverEg/server.asp
HTTP/1.1\r\nUser-Agent: Sourcelight Technologies py-
xmlrpc-0.8.7\r\nHost: 192.9.200.225:80\r\nContent-
Type: text/xml\r\nContent-length: 175\r\n\r\n<?xml
version="1.0"?
>\r\n<methodCall>\r\n\t<methodName>helloWorld</methodNa
me>\r\n\t<params>\r\n\t\t<param>\r\n\t\t\t<value><strin
g>eric</string></value>\r\n\t\t</param>\r\n\t</params>\ r\n</methodCall>'
11/08/2001 11:01:54 <source 192.9.200.225:80 fd 3>
client connection succeeded
11/08/2001 11:01:54 <source 192.9.200.225:80 fd 3>
client wrote 349 of 349 bytes
11/08/2001 11:01:54 <source 192.9.200.225:80 fd 3>
client finished writing request
11/08/2001 11:01:54 <source 192.9.200.225:80 fd 3>
client read 0 bytes of header and body
11/08/2001 11:01:54 <source 192.9.200.225:80 fd 3>
client read 89 bytes of header and body
11/08/2001 11:01:55 <source 192.9.200.225:80 fd 3>
client read 458 bytes of header and body
No Content-length parameter found
reading to EOF...
11/08/2001 11:01:55 <source 192.9.200.225:80 fd 3>
client finished reading header
11/08/2001 11:01:55 <source 192.9.200.225:80 fd 3>
client bodylen should be -1
11/08/2001 11:01:55 <source 192.9.200.225:80 fd 3>
client read 369 of -1 bytes of body

I did a little investigation and noticed that IIS
always sends a "continuation header" in its response.
I think this may be goofing up the response handling.

When I use IIS with a different client library,
xmlrpclib, things work fine.

I've also looked at the body of the response being
sent from IIS, and I believe it is a valid XMLRCP
response.

So my suspicions are strongly leaning towards
problems handling the HTTP protocol.

Discussion