Really its annoying that the creating a DTML Document results in a redirect for this reason. I would either: a) catch the error at your xmlrpc client and assume in this instance a redirect is fine or b) change the DTML Document not to return a redirect if its an xmlrpc request. This way if some other method has to return a redirect in xmlrpc for a good reason, you will still be able to catch it, rather than the server swallow the result. -- Andy McKay Agmweb Consulting http://www.agmweb.ca ----- Original Message ----- From: "Marco Aurelio Catunda Martins" <catunda@embratel.net.br> To: <zope@zope.org> Sent: Saturday, August 31, 2002 2:55 PM Subject: [Zope] xmlrpc redirect response
Hello,
When I try to adding an DTML Document by xmlrpc call the following error appear:
xmlrpclib.ProtocolError: <ProtocolError for localhost:8080/RPC2: 302 Moved Temporarily>
The 302 error code is about redirect response. I think there is no make sense redirect in xmlrpc call, so change zope source. I put the following method at Response class in xmlrpc.py file:
def redirect(self, location, status=302, lock=0): pass
What do you think about it? Is there any problem?
-- Marco Catunda
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )