Author ggenellina
Recipients
Date 2007-06-02.01:19:14
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Copying a reply from Tijs <tijs_news@artsoftonline.com> posted at c.l.p. <http://permalink.gmane.org/gmane.comp.python.general/524601>:

---
After having a quick look at your files, I conclude that the problem is in a
combination of two problems:

1. Your server is crap. It answers an HTTP/1.0 request by an HTTP/1.1
response without specifying any Connection header and without closing the
connection. Normally, a simple client that is not HTTP/1.1-aware expects
the connection to close. HTTP/1.1 leaves the connection open by default.

2. The Python implementation of xmlrpc is not very robust. It just waits for
the connection to close. A well-written client (like your Java client)
would detect the presence of a Content-Length header and use that. 

The other request is OK because the server closes the connection after
having sent the response. Why the difference? Don't know, but it is
something server-side. 

Try to force the server to send HTTP/1.0 responses, or turn off keep-alive,
or something like that. Otherwise, adapt xmlrpclib.py to robustly handle
1.1 responses.
---
History
Date User Action Args
2007-08-23 14:54:18adminlinkissue1727418 messages
2007-08-23 14:54:18admincreate