When the HTTP crawler encounters a client error (status codes 400–499), it immediately treats the response…
When the HTTP crawler encounters a client error (status codes 400–499), it immediately treats the response…: a task in LegoFlow-SWE (Harbor dataset). All 4xx responses are unconditionally treated as non‑retryable errors. The retry logic does not check either additional http error status codes or…
The task
All 4xx responses are unconditionally treated as non‑retryable errors. The retry logic does not check either `additional_http_error_status_codes` or `ignore_http_error_status_codes` for client error codes, so the configuration is silently ignored. This is inconsistent with how server errors (5xx) are handled.
Part of Lego-X/LegoFlow-SWE.