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 9765 - Include the error status code in the report when tests cannot be run
Summary: Include the error status code in the report when tests cannot be run
Status: NEW
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Web interface (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 enhancement
Target Milestone: ---
Assignee: fd
QA Contact: fd
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-18 10:16 UTC by fd
Modified: 2010-05-18 10:16 UTC (History)
0 users

See Also:

Attachments

Description fd 2010-05-18 10:16:29 UTC 
When the resource under test returns a 406, the mobileOK Checker only says that the tests could not be run because the resource under tests could not be retrieved.

A 406 may for instance be returned because of the specific HTTP headers sent by the mobileOK Checker, and actually browsing the page with a regular browser may well return a 200 in that case, which is really confusing for users.

The status code that was received should be displayed to help authors understand what happened.