chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Müller <>
Subject Re: Chunked transfer encoding
Date Tue, 07 May 2013 11:09:36 GMT
 Hi Carlo,

 We could add something here, but that is usually not necessary. HTTP 
 1.1 clients should be able to deal with chunks. And even if we do it, 
 the app server could decide to remove the Content-Length header again if 
 it, for example, compresses the outgoing stream.

 Could you describe your use case? Are you looking for general switch or 
 a hint per document?


> Dear chemists,
> we are trying to have our OpenCMIS based server produce HTTP response 
> with
> a Content-Length header and without the Transfer-encoding: chunked 
> one. It
> appears to me that the default behavior stems from OpenCMIS never 
> setting
> the Content-length, letting the app server use the default chunked 
> encoding
> in such cases. Is there any way we can at least hook to properly set 
> the
> Content-length at least for the getContentStream REST operation?
> Thanks,
> c.

View raw message