cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-5508) Bug CXF-4231 is back since 2.7.6
Date Fri, 24 Jan 2014 17:19:46 GMT


Sergey Beryozkin commented on CXF-5508:

Hi Jan,

I've looked at
" When a client desires to update one or more
   stored responses that have entity-tags, the client SHOULD generate an
   If-None-Match header field containing a list of those entity-tags
   when making a GET request; this allows recipient servers to send a
   304 (Not Modified) response to indicate when one of those stored
   responses *matches* the selected representation."

In other words, the server sends a new representation if we have no matches.
I think it is correct, right ?

In your case you do have tags matching. And ResponseImpl.evaluateIfNonMatch() returns null
to indicate a match which is wrong, if we have a match in If-None-Match case then it means
we do need a non-null ResponseBuilder to suggest that no resources have been modified. So
I think you are right, the only thing is that the fix needs to be done inside ResponseImpl.evaluateIfNonMatch(),
it should return the opposite value of the matching result...  

Thanks, Sergey

> Bug CXF-4231 is back since 2.7.6
> --------------------------------
>                 Key: CXF-5508
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.6
>            Reporter: Jan Engehausen
> The problem I reported in is back since
2.7.6; we noticed when upgrading to 2.7.8. See also
> 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

View raw message