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 6963 - CACHING-6: improve code extract
Summary: CACHING-6: improve code extract
Status: RESOLVED FIXED
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Java Library (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 enhancement
Target Milestone: ---
Assignee: fd
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-27 10:18 UTC by fd
Modified: 2010-04-26 12:35 UTC (History)
0 users

See Also:


Attachments

Description fd 2009-05-27 10:18:06 UTC
The returned code extract may be:
 Resource under test - invalid value ""

This is most probably triggered by the fact that the Checker is not looking at the right place to return the position. Be more explicit that the value should probably be looked for in the meta element or in the HTTP headers.

see for instance the report for:
 http://www.w3.org/2008/08/mok-check-tests/1.html
Comment 1 fd 2010-04-26 12:31:00 UTC
Incorrect value was not returned when the messages was triggered by a meta http-equiv element.

I updated the message to also return the origin of the message. Message now returned is:
[[ A cache related header or a meta http-equiv value ("Cache-Control" meta http-equiv) contains an invalid value (no-cache, foobar) ]]