----- Original Message ----- From: "Andreas Jung" <lists@zopyx.com> To: "Jonathan (dev101)" <dev101@magma.ca> Cc: <zope@zope.org> Sent: Friday, July 10, 2009 4:30 PM Subject: Re: [Zope] Problem with POST and text/xml
https://bugs.launchpad.net/zope2/+bug/373663
-aj
On 10.07.09 21:24, Jonathan (dev101) wrote:
I need to support a third party web service (which is not within my control) that wants to send xml data to my zope server (Zope 2.9.2 running on Redhat linux).
When Zope receives a POST request with a Content-Type of text/xml it assumes that it is an xmlrpc call (which it is not - it is just passing xml data within the POST request).
Is there a way to get Zope to turn off this "xmlrpc assumption" so that my zope external method can process the xml data that is being passed?
Thanks,
Jonathan
Thanks for the link! There were some differences between my Zope 2.9.2 installation and the patch instructions: 1) There was no interfaces.py file in the ZPublisher source directory (so I created a new one) 2) There were some differences in the HTTPRequest.py file, but it was still possible to make the changes indicated in the patch instructions. I restarted Zope via the ZMI, and ran a test (which generated a 500 response error). I noticed that there were no pyc/pyo files for interfaces.py and HTTPRequest.py, so I created them manually using py_compile. I restarted Zope and ran another test (using wget to simulate a POST request containing xml data) and got a 503 response: ---response begin--- HTTP/1.0 503 Service Unavailable Server: Zope/(Zope 2.9.2-, python 2.4.2, linux2) ZServer/1.1 Date: Sat, 11 Jul 2009 14:04:08 GMT Bobo-Exception-Line: 402 Content-Length: 995 Bobo-Exception-Value: See the server error log for details Content-Type: text/html; charset=iso-8859-15 Bobo-Exception-Type: NameError Connection: Keep-Alive Bobo-Exception-File: HTTPRequest.py There were no entries in Z2.log or event.log. Other than manually creating pyc/pyo files and re-starting zope, is there anything else I need to do to implement the changes to interfaces.py and HTTPRequest.py? If not, any ideas as to what could be causing this error or how I could go about debugging it? Thanks, Jonathan