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?
Florian
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.
