This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6828 - HTTP_RESPONSE-1 not triggered properly on network and/or DNS errors
Summary: HTTP_RESPONSE-1 not triggered properly on network and/or DNS errors
Status: RESOLVED FIXED
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Java Library (show other bugs)
Version: unspecified
Hardware: Other All
: P2 normal
Target Milestone: ---
Assignee: fd
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 16:53 UTC by fd
Modified: 2009-04-16 17:08 UTC (History)
0 users

See Also:

Attachments

Description fd 2009-04-16 16:53:56 UTC 
Description
-----
We do not have any generic way to represent a network error in a moki representation. The only thing we have so far is the HTTP_RESPONSE-1 code that appears in an HTTPerror element in an HTTPResponse element, and that is specific to the HTTP scheme.

The new version creates a FailedRetrievalElement whenever a network error occurs, but since it cannot be represented in the moki, there is no final error message in the report.

TODO
-----
Rollback a bit and create an HttpRetrievalElement with a NETWORK_ERROR status code as in previous version so that an HTTPerror element be issued.
Comment 1 fd 2009-04-16 17:08:17 UTC 
Rolled back to former way of issuing HTTPerror elements.

New regression test added to the test suite:
LINK_TARGET_FORMAT 8