404 errors caused by xml-rpc calls are masked

Bug #142832 reported by netchan
2
Affects Status Importance Assigned to Milestone
Zope 2
Won't Fix
Medium
Unassigned

Bug Description

When trying to access a nonexistent object/method, lib/python/ZPublisher/xmlrpc.py sets the status code 200 and sends back a regular xml-rpc Fault, with the standard 'Cannot locate object' message in html format as the body of the Fault.
The attached patch solves the problem if the variable 't' in method 'exception' is a zException.NotFound. Additional check for t=='NotFound' might be necessarry.

Revision history for this message
netchan (netchan) wrote :
Revision history for this message
Sascha Welter (betabug) wrote :

The patch is missing the following line:

from zExceptions import NotFound

Also note that apparently the xmlrpc specs tell us **not** to return a 404. The problems is that some spammers who try to abuse xmlrpc won't get it when we don't return a 404, so for the moment I've applied the patch to my own server.

Revision history for this message
Tres Seaver (tseaver) wrote :

We won't be applying the spec-violating patch.

Changed in zope2:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.