Description
You cannot use a standalone server to serve BadContent via XMLRPC.
Steps to reproduce
Set your BadContent source to a server driven by the standalone code and wonder.
Details
This wiki on standalone.
Workaround
Use Twisted etc.
Discussion
This seems to be a deadlock. The read() call in the wikirpc server blocks.
Maybe this is related to the usage of timeoutsocket because it changes the blocking semantics of the socket in a complex way.
Fixed by using content-length instead of relying on socket shutdown on client side (which doesn't happen with python xmlrpclib 8( ).
Plan
- Priority: Low
Assigned to: AlexanderSchremmer
- Status: fixed in patch-615