XML-RPC incorrect 404 return code
Hi, I'm doing some stuff using Zope as an XML-RPC server, and have come across a rather interesting bug. If the method doesn't exist on the Zope server, Zope returns an xmlrpclib.Fault with a faultCode= -1. This completely trips out my XML-RPC client which was rather expecting an xmlrpclib.ProtocolError. Does anybody have a strong opinion on sorting out ZPublisher.xmlrpc.py to to do a little more than it's present rather lame error handling?? Alan
I reported this a few month ago with a patch and was told that it'll be applied 'soon': http://collector.zope.org/Zope/1175 IMHO the xml-rpc error handling is a mess. You can't define your own standard_error_message like method, sometimes it returns html code, sets the status code to 200 even if there's an error, etc. Is there an intention to fix these in 2.X? Regards, Sandor
-----Original Message----- From: zope-dev-bounces@zope.org [mailto:zope-dev-bounces@zope.org] On Behalf Of Alan Milligan Sent: Thursday, May 06, 2004 9:41 PM To: zope-dev@zope.org Subject: [Zope-dev] XML-RPC incorrect 404 return code
Hi,
I'm doing some stuff using Zope as an XML-RPC server, and have come across a rather interesting bug.
If the method doesn't exist on the Zope server, Zope returns an xmlrpclib.Fault with a faultCode= -1.
This completely trips out my XML-RPC client which was rather expecting an xmlrpclib.ProtocolError.
Does anybody have a strong opinion on sorting out ZPublisher.xmlrpc.py to to do a little more than it's present rather lame error handling??
Alan
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
zope@netchan.cotse.net wrote:
IMHO the xml-rpc error handling is a mess. You can't define your own standard_error_message like method, sometimes it returns html code, sets the status code to 200 even if there's an error, etc. Is there an intention to fix these in 2.X?
You appear to have an itch... and you know what open source says about itches ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Thu, 6 May 2004 22:30:49 -0500 <zope@netchan.cotse.net> wrote:
I reported this a few month ago with a patch and was told that it'll be applied 'soon': http://collector.zope.org/Zope/1175
Who told you that? I see no comment on that issue.
IMHO the xml-rpc error handling is a mess. You can't define your own standard_error_message like method, sometimes it returns html code, sets the status code to 200 even if there's an error, etc. Is there an intention to fix these in 2.X?
By all means become a Zope contributor and fix this. That is the best way to get things the way you want them. See: http://dev.zope.org/CVS/ContributorIntroduction -Casey
On Fri, 2004-05-07 at 09:33, Casey Duncan wrote:
On Thu, 6 May 2004 22:30:49 -0500 <zope@netchan.cotse.net> wrote:
I reported this a few month ago with a patch and was told that it'll be applied 'soon': http://collector.zope.org/Zope/1175
Who told you that? I see no comment on that issue.
That might have been me via IRC, IIRC. If I didn't apply it, it's because I didn't immediately do so (either because I wanted to review it further or I just didn't have time), but in any case I apologize... please do resubmit the patch to the collector. I can't promise it will be applied quickly but it won't be dropped completely off the radar again. - C
participants (5)
-
Alan Milligan -
Casey Duncan -
Chris McDonough -
Chris Withers -
zope＠netchan.cotse.net