This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-1978 LC-1979 LC-1980 LC-1981 LC-1991 LC-1992 LC-2159
Next: LC-1992
* About the treatment of HTTP Status 401: - Why should tests be applied to the response body of such an HTTP response? The body will never be touched by any browser during the first pass (when authentication credentials have not already been sent) AFAICT. Besides, it wouldn't make any sense to display the resource if it's an included image for instance. It's perfectly normal to count the response in EXTERNAL_RESPONSE and PAGE_SIZE_LIMIT, but I suggest updating the "Carry out tests on the response" to "Do not carry out tests on the response", especially given the fact that the tests FAIL when credentials are wrong (and so there's no need to test the response body anyway even for the second pass) - "Re-request the resource using authentication information" could deserve some clarification. What if the checker doesn't have any authentication information? I would clarify this with "Re-request the resource using authentication information if available or FAIL" (where FAIL would be HTTP_RESPONSE-7)