- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Mon, 19 Feb 2007 12:01:42 +0100
- To: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
- Cc: public-wai-ert@w3.org
Hi, Carlos Iglesias wrote: > > Carlos Iglesias schrieb: >>> 2.3.3 HTTP Response >>> >>> "If an HTTP request fails for any reason during a test >> (network-level error, DNS resolution error, non-HTTP >> response, or server returns an HTTP 4xx or 5xx status), the >> test outcome should be considered FAIL" >>> When not reaching the server it should be a not tested >> instead a fail (e.g 5xx server errors). >> >> Why is 5xx is mentioned here? > > My understood of our discussion was that if you don't reach a resource > to test, then it should be a not tested. > 5xx are Server Errors in which the server is incapable of performing the > request. Unless there is a mobileOK provision that says something like "server errors must never occur", you can (and should) evaluate any *content* received from the server. I don't see any exceptions for error messages sent by the server (or the application either). Maybe we should clarify that in our comments to the MWI folks and ask them to specify more explicitly what should happen with error messages. Agreed? Regards, Shadi -- Shadi Abou-Zahra Web Accessibility Specialist for Europe | Chair & Staff Contact for the Evaluation and Repair Tools WG | World Wide Web Consortium (W3C) http://www.w3.org/ | Web Accessibility Initiative (WAI), http://www.w3.org/WAI/ | WAI-TIES Project, http://www.w3.org/WAI/TIES/ | Evaluation and Repair Tools WG, http://www.w3.org/WAI/ER/ | 2004, Route des Lucioles - 06560, Sophia-Antipolis - France | Voice: +33(0)4 92 38 50 64 Fax: +33(0)4 92 38 78 22 |
Received on Monday, 19 February 2007 11:02:08 UTC