cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Engehausen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5508) Bug CXF-4231 is back since 2.7.6
Date Fri, 24 Jan 2014 06:26:37 GMT

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

Jan Engehausen commented on CXF-5508:
-------------------------------------

Hi Sergey,

okay I still think there's an issue here: We're using http://docs.oracle.com/javaee/6/api/javax/ws/rs/core/Request.html#evaluatePreconditions%28java.util.Date,%20javax.ws.rs.core.EntityTag%29
and pass in a weak ETag value (with {{If-None-Match}} header) and the last modified timestamp
(with {{If-Modified-Since}} header) - the values are obtained from a previous request. Neither
ETag value nor timestamp have changed. In my opinion the preconditions are *not* met; ETag
values match, but we say "send request if ETag does not match or resource has been modified",
in this case a non-{{null}} value should be returned by {{evaluatePreconditions(Date, EntityTag)}}
- currently {{null}} is returned, making us send a completely fresh response instead of status
code 304.
What do you think?

Kind regards,
Jan

> Bug CXF-4231 is back since 2.7.6
> --------------------------------
>
>                 Key: CXF-5508
>                 URL: https://issues.apache.org/jira/browse/CXF-5508
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.6
>            Reporter: Jan Engehausen
>
> The problem I reported in https://issues.apache.org/jira/browse/CXF-4231 is back since
2.7.6; we noticed when upgrading to 2.7.8. See also https://fisheye6.atlassian.com/browse/cxf/branches/2.7.x-fixes/rt/frontend/jaxrs/src/main/java/org/apache/cxf/jaxrs/impl/RequestImpl.java?r2=1503661&r=1494596
> The concrete change/problematic part: if (rb != null) { => if (rb == null) {
> Any chance for a fix in the next release?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message