You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Carlo Sciolla (JIRA)" <ji...@apache.org> on 2013/05/08 09:59:16 UTC
[jira] [Updated] (CMIS-655) Chunked transfer encoding effectively
disables browser caching
[ https://issues.apache.org/jira/browse/CMIS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlo Sciolla updated CMIS-655:
-------------------------------
Issue Type: Improvement (was: Bug)
> Chunked transfer encoding effectively disables browser caching
> --------------------------------------------------------------
>
> Key: CMIS-655
> URL: https://issues.apache.org/jira/browse/CMIS-655
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.9.0 beta 1
> Reporter: Carlo Sciolla
>
> OpenCMIS never sets the Content-length on HTTP responses, letting the app server use the default strategy of sending them with a "Transfer-encoding: chunked" header.
> While it's valid HTTP 1.1, it's not fully supported by e.g. some browsers and cache middleware, which handle such responses fine but fail to cache them.
> Please provide to either set the content-length at least in the getContentStream calls, or allow users to hook into the HTTP serialization process.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira