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

RE: [Bug 5537] Checker aborts on bad URI in redirect

From: Abel Rionda <abel.rionda@fundacionctic.org>
Date: Fri, 7 Mar 2008 14:49:42 +0100
Message-ID: <09700B613C4DD84FA9F2FEA52188281903123BCD@ayalga.fundacionctic.org>
To: "Sean Owen" <srowen@google.com>, "public-mobileok-checker" <public-mobileok-checker@w3.org>

Hi folks,

As far as we know, this error is currently solved. (HTTP Resource class
catches all possible exceptions hierarchy and wraps them into a generic
HTTPRedirect.NETWORK_ERROR). Perhaps we should have a more fine-grained 
error treatment on this.

Abel and Miguel.

-----Mensaje original-----
De: public-mobileok-checker-request@w3.org
[mailto:public-mobileok-checker-request@w3.org] En nombre de Sean Owen
Enviado el: viernes, 07 de marzo de 2008 3:35
Para: public-mobileok-checker
Asunto: Re: [Bug 5537] Checker aborts on bad URI in redirect

Question on this one -- according to the code this is kinda intended
behavior. If the last request ended in some kind of exception we
assume we don't actually have a document to test, so there are no
results to report.

I kind of agree with this and recall a long argument on a whiteboard
about this. Just checking, what do people think about the right
behavior here? Garbage in, garbage out, I say, so I am not
particularly concerned if a situation like this results in an
exception (subsequently, looks like a change has turned this internal
exception into a more appropriate TestException), or if it becomes
some meaningless test results stating that the result is fail fail
fail because the body is empty and all kinds of screwed up as a
result. Just a different garbage out.

I'm happy to 'fix' this, just want to know if everyone agrees with
that, or whether this needs discussion.


On Thu, Mar 6, 2008 at 11:40 AM,  <bugzilla@farnsworth.w3.org> wrote:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=5537
>            Summary: Checker aborts on bad URI in redirect
>            Product: mobileOK Basic checker
>            Version: unspecified
>           Platform: PC
>         OS/Version: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: Java Library
>         AssignedTo: srowen@google.com
>         ReportedBy: dom@w3.org
>  similar to #5536, when we try to resolve a URI for a redirect, the
>  aborts with the following trace when the URI is invalid:
>  xception in thread "main" java.lang.IllegalArgumentException: Invalid
>  Invalid query
>         at
>         at
>         at
>  org.w3c.mwi.mobileok.basic.HTTPResource.<init>(HTTPResource.java:110)
>         at
>         at
>         at
>         at
>         at org.w3c.mwi.mobileok.basic.Tester.main(Tester.java:191)
>  This would again be better reported as HTTP_RESPONSE-1
Received on Friday, 7 March 2008 13:49:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:20 UTC