[DM] Making XMLRPC protocol selection smarter
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.
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.
Changed in zope2: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Workaround published on PyPI: "dm.zopepatches .xmlrpc"