[DM] Making XMLRPC protocol selection smarter

Bug #373663 reported by Andreas Jung
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Wishlist
Andreas Jung

Bug Description

2. Introduction

Zope seems very proud of its embedded xmlrpc implementation. Whenever it receives a POST request with a content type starting with text/xml it is convinced that this cannot be something else than an xmlrpc request. Of course, it is wrong. There are many non xmlrpc request types that look like this, e.g. SOAP requests.

3. Feature

Define a new interface ZPublisher.interfaces.IXmlrpcChecker with method __call__.

When a request might be an xmlrpc request (according to the criteria above), check for an IXmlrpcChecker utility and call it with the current request to determine whether the request should be interpreted as an xmlrpc request. If there is no such utility, interpret the request as xmlrpc.

4. Example Use Cases

Essential to handle SOAP requests, e.g. the SOAP requests of the XStandard editor.

Revision history for this message
Andreas Jung (ajung) wrote :
Changed in zope2:
assignee: nobody → Andreas Jung (ajung)
Revision history for this message
Dieter Maurer (d.maurer) wrote :

Workaround published on PyPI: "dm.zopepatches.xmlrpc"

Changed in zope2:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: Confirmed → Invalid
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.