Return-Path: X-Original-To: apmail-chemistry-dev-archive@www.apache.org Delivered-To: apmail-chemistry-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 10A77D593 for ; Tue, 14 May 2013 14:45:16 +0000 (UTC) Received: (qmail 30701 invoked by uid 500); 14 May 2013 14:45:15 -0000 Delivered-To: apmail-chemistry-dev-archive@chemistry.apache.org Received: (qmail 30636 invoked by uid 500); 14 May 2013 14:45:15 -0000 Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@chemistry.apache.org Delivered-To: mailing list dev@chemistry.apache.org Received: (qmail 30626 invoked by uid 99); 14 May 2013 14:45:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 14:45:15 +0000 Date: Tue, 14 May 2013 14:45:15 +0000 (UTC) From: =?utf-8?Q?Florian_M=C3=BCller_=28JIRA=29?= To: dev@chemistry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CMIS-655) Chunked transfer encoding effectively disables browser caching MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CMIS-655?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Florian M=C3=BCller resolved CMIS-655. --------------------------------- Resolution: Fixed Fix Version/s: OpenCMIS 0.9.0 =20 > 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 > Fix For: OpenCMIS 0.9.0 > > > 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.=20 > 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 t= hem.=20 > Please provide to either set the content-length at least in the getConten= tStream 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 administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira