chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Müller <>
Subject Re: [OpenCMIS] Possibility to disable chunked transfer encoding
Date Thu, 18 Sep 2014 12:41:36 GMT
Hi Sascha,

To turn off chunking OpenCMIS would have to know how big the request 
body is before it sends it. The Content-Length header must be set before 
the request body is sent.
To determine the length, the body would have to be generated and stored 
somewhere. And here is the issue. The body can be fairly large, 
especially if it contains a document. Keeping it in main memory could 
become a problem if you want to upload a 5GB video file. So, OpenCMIS 
would have to put it into a temporary file and read it again afterwards. 
The performance impact would be immense.
To cut a long story short, there is no switch in OpenCMIS to disable 

You can, however, implement your own HttpInvoker class. This class is 
responsible for the HTTP connection. You can implement all these things 
that I described above there and make sure that chunking is turned off.
Not sure if that solves your issue, though. You might have the same 
problem with other CMIS clients.

- Florian

> Hello together,
> is it possible to disable the chunked transfer encoding in Java 
> OpenCMIS ?
> I am asking because our Nginx based Connect-Cluster currently does not
> support Chunks and adjusting the Cluster affects our whole public
> available systems (also I am not sure if our FW will handle chunks
> properly).
> On client side I already use non PartialContentStream to avoid chunks
> but I also noticed a „Length-Required“ exception when calling the
> query discovery service.
> So now I am trying to estimate the efforts and benefits of either
> adjusting the Nginx cluster or disabling chunks at OpenCMIS (if
> possible at all).
> Thx in advance.
> Cheers
> Sascha

View raw message