v3.2.0: Better error messages

Release Notes:

This release makes the archiver significantly smarter and more resilient by introducing intelligent, context-aware error handling. The script now understands the difference between temporary API issues and permanent, unrecoverable failures.

This update dramatically improves the success rate for large archives by automatically retrying jobs that fail due to transient server-side problems. For permanent failures, the tool now provides clear, human-readable explanations, giving users actionable feedback to diagnose issues with their URLs.

There are no breaking changes in this release.

What's New

• Automatic Retries for Transient Errors: The archiver no longer gives up on temporary failures. If a job fails due to issues like a server timeout (504 Gateway Timeout), rate-limiting (429 Too Many Requests), or temporary system overload (503 Service Unavailable), the URL is now automatically re-queued for another attempt later in the run.

• Clear, Actionable Explanations for Permanent Failures: Instead of a generic error, the script now provides a specific, helpful explanation for permanent failures. You will now see clear messages for common problems like:

  • The page could not be found (404 Not Found).
  • The URL has too many redirects, likely indicating a redirect loop.
  • The domain name could not be found. Check for typos in the URL.

• Helpful Hints in Error Messages: For errors where a solution exists within the tool, the message will now provide a hint. For example, if a page fails with a 404 Not Found or 403 Forbidden error, the log message will now suggest using the --capture-all flag to save the error page itself.