Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Thu, 18 Sep 2014 08:56:33 +0000 (UTC)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12740691.1410414294000.64435.1411030593922@Atlassian.JIRA>
In-Reply-To: <JIRA.12740691.1410414294000@Atlassian.JIRA>
References: <JIRA.12740691.1410414294000@Atlassian.JIRA>
 <JIRA.12740691.1410414294606@arcas>
Subject: [jira] [Commented] (CXF-5996) respect client cache headers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138707#comment-14138707 ] 

Sergey Beryozkin commented on CXF-5996:
---------------------------------------

The reader interceptor should not give the response, the request filter has already given the response from the cache, right ? Sorry, may be I do not understand the goal of the reader, but I thought it would only block the process of the de-serialization because it is not needed if the response entity object has been found in the local cache.

Cheers, Sergey

> respect client cache headers
> ----------------------------
>
>                 Key: CXF-5996
>                 URL: https://issues.apache.org/jira/browse/CXF-5996
>             Project: CXF
>          Issue Type: New Feature
>            Reporter: Romain Manni-Bucau
>         Attachments: client-jaxrs-cache-control.zip, client-jaxrs-cache-control.zip
>
>
> Hi
> would be great to get a mecanism (maybe using jcache as abstraction) to respect on client side http cache headers


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)