RE: Recent updates regarding pending bugs

Hi folks,

 

Following with the changes commented bellow; we have been making more
changes in relation to:

 

>No errors on HTTP errors
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5358

>We have modified Preprocessor Results  for this purpose. In moki
document, at the end of each HTTP Response there is a new element 

>(<HTTPerror code="HTTP_Response_*"  severity="FAIL|WARM">).It is
pending to do a >XSLT function to check this value in those where are 

>required to inform about this
(http://www.w3.org/TR/mobileOK-basic10->tests/#http_response
<http://www.w3.org/TR/mobileOK-basic10-%3etests/#http_response> ).  

 

But before committing them, we consider necessary discussing the way we
are doing them. 

In general HTTP errors (HTTP_Response_*) can be divided into two
classes:

 

1.-Those that affect the rest of resources, except the main document.

 

 The checking in this case is made inside each required test through a
XSLT template. For example, in case of launching the test
LINK_TARGET_FORMAT

 against a linked resource with bad character encoding and HTTP not
found error response, we would have the following test result:

 

<?xml version="1.0" encoding="UTF-8"?>

<tests outcome="PASS">

   <test name="LINK_TARGET_FORMAT" outcome="PASS">

      <result name="LINK_TARGET_FORMAT-2" outcome="WARN">

         <info>WARN: The linked resource
http://www.w3c.es/HTTP_RESPONSE-9.html is served with a character
encoding (iso-8859-1) that may not be appropriate for a mobile
device</info>

      </result>

      <result name="HTTP_RESPONSE-9" outcome="WARN">

         <info>WARN: The HTTP status code is 404 or 5xx (in response to
the resource http://www.w3c.es/HTTP_RESPONSE-9.html) and the response
relates to a request for a linked resource </info>

      </result>

   </test>

</tests>

 

2.-Those that affect the main document.

 

In this case we do not have a specific test for checking this, so we
have defined a new test that join all HTTP_RESPONSE_* errors for the
main document. For example:

 

<tests outcome="FAIL">

   <test name="MAIN_DOCUMENT_HTTPERRORS" outcome="FAIL">

      <result name="HTTP_RESPONSE-1" outcome="FAIL">

         <info>FAIL: The request to the resource
http://www.noexistnoexist.com does not result in a valid HTTP response
(because of network-level error, DNS resolution error, or non-HTTP
response) </info>

      </result>

   </test>

</tests>

 

 

What do you think of this approach? If you agree that is the suitable
one, we will commit the changes soon.

 

Regards,

 

Miguel and Abel.

 

  

________________________________

De: public-mobileok-checker-request@w3.org
[mailto:public-mobileok-checker-request@w3.org] En nombre de Abel Rionda
Enviado el: jueves, 17 de enero de 2008 14:53
Para: public-mobileok-checker@w3.org
Asunto: Recent updates regarding pending bugs

 

Hi all,

 

We have commited some changes regarding the bugs that are assigned to
us. Basically these are 

the following:

 

*	Missing detection of HTML namespace
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5359 

We have added a node in moki with this signature (<xmlNamspace
declaration="true|false">). Additionaly, the XSLT page

      is also modified and the related test case
(ContentFormatSupportTest/10).

 

*	No errors on HTTP errors
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5358

We have modified Preprocessor Results  for this purpose. In moki
document, at the end of each HTTP Response there is a new element 

(<HTTPerror code="HTTP_Response_*"  severity="FAIL|WARM">).It is pending
to do a XSLT function to check this value in those where are 

required to inform about this
(http://www.w3.org/TR/mobileOK-basic10-tests/#http_response).  

 

*	Manage HTTP basic authentication
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5138

We have added two configuration parameters to Tester class and
authentification logic in HTTPResource 

 

*	https: handle expired certificates and warn
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5022 

We have added Apache sample contribution as SSL implementation(i.e
EasySSLProtocolSocketFactory). In addition, we have implemented 

      a certificate validator in order to fulfill mobileOK
requierements.

 

 

Regarding tests cases, you should rebuild the moki files using
CreateMasterTestOutput.

 

The changes are provisonally for the moment,perhaps they will need
further refinement and testing.

 

 

Best regards,

Abel and Miguel