Hi Bill,
Heads up: I have recently modified code with respect to this area, see:
https://jersey.dev.java.net/issues/show_bug.cgi?id=228
but i have not done anything in relation to what you have observed.
Paul.
On Feb 20, 2009, at 9:31 AM, Paul Sandoz wrote:
> Hi Bill,
>
>
> On Feb 19, 2009, at 10:51 PM, Bill de hOra wrote:
>
>> In jersey 1.0.1 the ResponseBuilder created to send back 304 sends
>> back the Etag header and not Last-Modified - is that intentional or
>> will I send in a patch?
>>
>
> Please, that would be most helpful.
>
> I just verified that there is an issue. Annoying in the unit tests i
> forgot to assert that the etag and data should be present:
>
> public void
> testIfNonMatchWithMatchingETag_IfModifiedSinceAfterLastModified() {
> initiateWebApplication(LastModifiedEtagResource.class);
> ClientResponse response = resource("/", false).
> header("If-None-Match", "\"1\"").
> header("If-Modified-Since", "Tue, 2 Jan 2007 00:00:00
> GMT").
> get(ClientResponse.class);
> assertEquals(304, response.getStatus());
> }
>
> Paul.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>