W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > October 2007

Re: ETag/Last-Modified tests

From: Sean Owen <srowen@google.com>
Date: Thu, 18 Oct 2007 12:08:31 -0400
Message-ID: <e920a71c0710180908m3cd386d5w67d7223495aa6afc@mail.gmail.com>
To: "Dominique Hazael-Massieux" <dom@w3.org>
Cc: public-mobileok-checker <public-mobileok-checker@w3.org>

You should be able to override headers by placing a "foo.headers" file
next to file "foo", containing "Name: Value" pairs on each line. I
would maybe not be surprised if Tomcat doesn't let you override these,
or re-sets them upstream, in which case we'll have to do something
more drastic.

On 10/18/07, Dominique Hazael-Massieux <dom@w3.org> wrote:
>
> Hi,
>
> I've fixed the way the caching tests for ETag and Last-Modified headers
> works; it used to say something was wrong if a resource sent back the
> same ETag or Last-Modified header - which is only wrong if the status
> code is not 304.
>
> The problem is that the associated unit tests (CACHING/9 and CACHING/10)
> now fails (presumably because the tomcat server does the right thing
> upon reading the headers), and I don't see how to make them mimic a
> wrong behavior. Does anyone have any suggestion?
>
> Dom
>
>
>
>
Received on Thursday, 18 October 2007 16:08:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:04 GMT