This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6110 - CACHING-6 check only performed on Cache-Control
Summary: CACHING-6 check only performed on Cache-Control
Status: RESOLVED FIXED
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Java Library (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Abel Rionda
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-23 11:50 UTC by fd
Modified: 2008-12-04 15:07 UTC (History)
0 users

See Also:

Attachments

Description fd 2008-09-23 11:50:04 UTC 
The CACHING-6 subtest is defined as:
[[ If any cache related header contains an invalid value, warn ]]

CachingTest.xsl only checks the value of the Cache-Control header (or equivalent meta http-equiv).

So, for instance, it does not check the ETag, Expires, and Last-Modified values.

The following:
 ETag: hello
should trigger CACHING-6 because the value of the ETag HTTP header must be a quoted string.
Comment 1 Abel Rionda 2008-09-25 09:07:07 UTC 
Now we check the values for the following cache related headers:

-Cache-control
-ETag
-Last-Modified
-Expires
Comment 2 fd 2008-12-04 15:07:27 UTC 
Additional fixes:
- CACHING-6 was returned most of the time because the check on ETag for instance was run with an empty value when there was no ETag header.
- isCanonicalDateValue always returned false since all the formats were checked.