mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #716] Question: Is there a way to retry a failed archive method on an existing snapshot? #452
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#452
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Karunamon on GitHub (Apr 19, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/716
Imagine archiving a website that discriminates against wget or curl as clients (sadly common). The usual fix for this is to change your user agent to omit any mention of those tools.
Once I've changed the user agent configuration setting, is there a way to retry only the failed archive method on an otherwise successful snapshot without rerunning the whole thing?
@pirate commented on GitHub (Apr 19, 2021):
It will never re-archive with methods that have previously succeeded, it only retries ones that failed previously. Just click Pull in the UI, or run
archivebox update https://example.com/snapshot/url/here.@Karunamon commented on GitHub (Apr 20, 2021):
Aha, wasn't aware of that behavior. Thanks!