[
https://issues.apache.org/jira/browse/CXF-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138742#comment-14138742
]
Sergey Beryozkin commented on CXF-5996:
---------------------------------------
Hi, so I guess it is about the current limitation of API where the filter
properties are not seen in readers ?
How about this:
1. Client request filter checks if the request can be satisfied locally, if not
- it lets it proceed, if no - it creates a Response and set a custom header on
this response, for example, "_LocalResponse_:true".
2. Reader interceptor checks if a "_LocalResponse_" header is available in the
Response, if yes - it removed "_LocalResponse_" from the headers and blocks the
reader interceptor chain, if no, then it delegates to the next interceptor.
Does it work ?
> 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)
