We just disabled the HTTP Fetch module for certain
per-host overrides, expecting the affected URIs to land
in the logs with either untried (0) or too-many-retries
(after being untried multiple times in a row) statuses.
Instead, a few had connect-failure statuses... which
are only set by the HTTP Fetcher itself. Thus these
must have been left over from a previous attempt of the
same URI.
This is misleading, and might cause problems in other
cases -- as a URI continues to be treated as if
something on a previous attempt had happened again.
Gordon Mohr
None
0.8.0
Public
|
Date: 2007-03-14 00:08
|
|
Date: 2004-04-15 22:23 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2004-04-15 22:23 | gojomo |
| resolution_id | None | 2004-04-15 22:23 | gojomo |
| close_date | - | 2004-04-15 22:23 | gojomo |
| artifact_group_id | None | 2004-03-31 01:12 | gojomo |
| assigned_to | nobody | 2004-03-30 23:30 | gojomo |