W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > January 2008

Dealing with HTTP errors

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Fri, 11 Jan 2008 14:17:20 +0100
To: public-mobileok-checker <public-mobileok-checker@w3.org>
Message-Id: <1200057440.7038.331.camel@localhost>

Hi,

As far I can tell, we don't have any code in place currently to report
the errors described in 
http://www.w3.org/TR/mobileOK-basic10-tests/#http_response
and
http://www.w3.org/TR/mobileOK-basic10-tests/#meta_http_equiv

Can someone confirm so?

If that's the case, this is definitely a todo item for moving to beta.

As I noted in one of my (numerous, sorry about that) other messages,
there is at least one case where an HTTP error is reported through an
individual test (GRAPHICS_FOR_SPACING); I'm thinking that when we
encounter an HTTP error, we probably shouldn't run the other relevant
tests on the said resource at all.

If so, maybe we should have something in the moki document to mark up
the resources that triggered an HTTP error (as defined as a fail in
#http_response), so that we can easily avoid them in the XSLT-based
tests.

Dom
Received on Friday, 11 January 2008 13:17:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 11 January 2008 13:17:52 GMT