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

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

Good morning Sergey,

I've tested 2.7.9-SNAPSHOT but unfortunately another scenario we test is not 
working any more now: Instead of a matching ETag value we send a non-matching 
one (e.g. "W/does-not-match", {{If-None-Match}}) and a matching last modified 
time stamp (same as from the original response, {{If-Modified-Since}}). In 
2.7.5, and to my expectation, this must return status code 200 (OK), a new 
response - because the ETags differ.

So to summarize: We have the service generate the same ETag and last 
modification time stamp returning all the time, and we have the following tests:

# send _same ETag value_ for {{If-None-Match}}, _same last modification date_ 
for {{If-Modified-Since}} - we expect 304 (not modified)
# send _different ETag value_ for {{If-None-Match}}, _same last modification 
date_ for {{If-Modified-Since}} - we expect 200 (ok, new response)

I think these are valid expectations, do you agree?

Thanks,
Jan

> Request.evaluatePreconditions(Date, EntityTag) loses a non-null 
> ResponseBuilder 
> --------------------------------------------------------------------------------
>
>                 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
>            Assignee: Sergey Beryozkin
>             Fix For: 3.0.0-milestone2, 2.6.12, 2.7.9
>
>
> 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)

Reply via email to