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: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Alan Milligan
> Sent: Thursday, May 06, 2004 9:41 PM
> To: [EMAIL PROTECTED]
> 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 - [EMAIL PROTECTED]
> 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-Dev maillist - [EMAIL PROTECTED]
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 )
