Using the client in eXist-db we encountered the issue that Transfer-Encoding: chunked is set automatically. When dealing with an REST service that is not able to parse chunked encoding (corpus delicti: python hug) we solved the issue by setting HTTP version to 1.0 by using an the undocumented attribute http-version within the request element. This solution is clearly a work around.
- Is there a way to disable the usage of chunked encoding?
- Why is this attribute not part of the documentation? Is it subject to be removed later on?
In addition it might be useful to get an overview of the rules to set the Transfer-Encoding header.
Using the client in eXist-db we encountered the issue that
Transfer-Encoding: chunkedis set automatically. When dealing with an REST service that is not able to parse chunked encoding (corpus delicti: python hug) we solved the issue by setting HTTP version to 1.0 by using an the undocumented attributehttp-versionwithin therequestelement. This solution is clearly a work around.In addition it might be useful to get an overview of the rules to set the
Transfer-Encodingheader.