Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not interpret all POST requests with "content-type=text/xml" as XML-RPC requests #620

d-maurer opened this issue May 13, 2019 · 1 comment


Copy link

commented May 13, 2019

Ancient versions of ZPublisher.HTTPRequest interpreted all POST requests with content-type text/xml as requests to be handled via the builtin XML-RPC support. Later, recognizing that SOAP may use such requests even though it should not be handled as an XML-RPC request, a special handling of SOAP requests was introduced. However, there are further requests with the above characteristics not to be handled by the buildin XML-RPC support. Examples are requests which should be handled by dm.zope.rpc -- a multi protocol rpc framework which supports different serialization types for input and output, e.g. XML input (leading to Content-Type=text/xml) and JSON output (which excludes the builtin XML-RPC).

ZPublisher.HTTPRequest should provide some control over the use of the builtin XML-RPC support.


This comment has been minimized.

Copy link

commented May 13, 2019

Fixed by merging #622

@dataflake dataflake closed this May 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.