ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior?
3.2 CACHING: Fail on Last-Modified, ETag header behavior?
- State:
- CLOSED
- Product:
- mobileOK Basic tests
- Raised by:
- Sean Owen
- Opened on:
- 2007-01-18
- Description:
- This is quite nearly minor enough to call an editorial decision, but not quite.
Safer to raise an issue for next week:
3.2 CACHING (http://www.w3.org/TR/mobileOK-basic10-tests/#test_caching) is
slightly inconsistent in that if your server disables caching by sending
\"Cache-Control: no-cache\", you get a warn, whereas if you effectively disable
caching by not handling conditional requests, you fail. Since the intent of the
test is to *require* caching-related information to be sent, but to merely
*encourage* making content cacheable, it is proposed that the last two fails in
the test be changed to warns. - Related Actions Items:
- No related actions
- Related emails:
- [minutes] Cambridge 2007 F2F meeting (from dom@w3.org on 2007-01-24)
- RE: ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from luca.passani@openwave.com on 2007-01-19)
- Re: ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from parcher@icra.org on 2007-01-19)
- RE: ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from k.scheppe@t-online.net on 2007-01-19)
- Re: ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from parcher@icra.org on 2007-01-19)
- Re: ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from dom@w3.org on 2007-01-19)
- ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from dean+cgi@w3.org on 2007-01-18)
- RE: ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from jo@linguafranca.org on 2007-01-18)
- Re: ISSUE-179: 3.2 CACHING: Fail on Last-Modified, ETag header behavior? (from srowen@google.com on 2007-01-18)
Related notes:
No additional notes.
Display change log