Hi Carlo,
That is surprising. Chunked encoding isn't really exotic.
Could you please open an Improvement issue and add a few details. I'll
look into it.
- Florian
Hi Florian,
our use cases currently revolve around caching. As an example, we
found out quite some browsers fail to cache HTTP responses when
encoded in chunks. The same applies to some intermediate cache
middleware between our CMIS repository and the browser.
It would be indeed great if we had some hooks in the serialization
process to influence the HTTP details of the CMIS responses before
they're sent back to the client, at least setting headers such as
Content-Length, Cache-Control, ETag, etc.
c.
2013/5/7 Florian Müller
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.
--
Carlo Sciolla
--==(A)==--
Linux User #372086
My personal blog: http://www.skuro.tk [2]
Follow me on twitter: http://twitter.com/skuro [3]
[4]Fork me on Github: http://github.com/skuro [5]
[6]My LinkedIn profile: http://nl.linkedin.com/in/carlosciolla [7]
--==(A)==--
Product Lead at Backbase - Next Generation Portal Software for
Financials & Large Enterprises (http://www.backbase.com [8])
Links:
------
[1] mailto:[email protected]
[2] http://www.skuro.tk
[3] http://twitter.com/skuro
[4] http://twitter.com/skuro
[5] http://github.com/skuro
[6] http://github.com/skuro
[7] http://nl.linkedin.com/in/carlosciolla
[8] http://www.backbase.com
