You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Thank you @mathias-goebel. It is rather the opposite, it is not part of the document because it was meant to be added.
@adamretter It might be a good idea to use the Github page publication mechanism (I think it would be something like expath.github.io, I am not sure how it works). So the website is entirely published from a repository in the EXPath group in Github. Unfortunately I can't do it myself, but if you think this would help, let's open a new issue and look for a volunteer :-)
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 attributehttp-version
within therequest
element. This solution is clearly a work around.In addition it might be useful to get an overview of the rules to set the
Transfer-Encoding
header.The text was updated successfully, but these errors were encountered: