Example resource that has (for us) this 304 -> 200 problem:
public Response
getContainerNotificationFeed(@HeaderParam(Constants.HEADER_IF_MODIFIED_SINCE)
Date ifModifiedSince) {
Response r = null;
Date lastCheck = new Date();
// /*
// * IF_MODIFIED_SINCE according to HTTP protocol contains time and
date without milliseconds. We truncate
// * milliseconds in order to not loose notifications generated
within one second.
// */
lastCheck.setTime(lastCheck.getTime() / 1000 * 1000);
r =
Response.status(Response.Status.NOT_MODIFIED).lastModified(lastCheck).build();
return r;
}
Tested that with the previous curl command, and still response has code 200
in it.
--
View this message in context: http://n2.nabble.com/1-1-4-response-codes-with-Atom-feeds-tp3998025p3998692.html
Sent from the Jersey mailing list archive at Nabble.com.