Hi chris, hi dieter, I also have this problem with using xmlrpc from a python client with zope.

...

RuntimeError: Syntax error at line 34: illegal character in content

This was the bane of one of our projects to the point where Andy re-wrote ZMailIn to no-longer use XML-RPC.

It's to do with stuff-which-should-probably-be-entities but we never tracked down what wasn't encoding something when it should have done. I'd blame the marshalling code in xmlrpclib.py myself.

If you ever fix this, do let us know :-)

I have a Zope 2.3.1 server running as well as a Zope 2.3.2. I developed an Service-Framework on the first and then tried to install it on the 2.3.2 .. it failed I printed out the raw data of the transmission and they differ: When I call the function on Zope-2.3.1 i get this response: --------------------------------------------------------- <?xml version='1.0'?> <methodResponse> <params> <param> <value><string>OK</string></value> </param> </params> </methodResponse> --------------------------------------------------------- when I call the same function on the same backend on Zope-2.3.2 I get the following: --------------------------------------------------------- X-Powered-By: Zope (www.zope.org), Python (www.python.org) Content-Length: 128 Connection: close Content-Type: text/xml <?xml version='1.0'?> <methodResponse> <params> <param> <value><string>OK</string></value> </param> </params> </methodResponse> --------------------------------------------------------- There is some header-information in the body (that perhaps shoudn't be there) Where there any changes in Zope 2.3.1 -> 2.3.2 in the Publishing part ?? With the second response the xmllib-parser won't work as we see. any suggestions to that ?? did you guy's updated to Zope-2.3.2 recently ?? thanks for any response and hope this helps a bit .. Ulrich Eck net-labs