mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #653] Question: Does Archivebox 0.5.6 still output static index.html? #1920
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#1920
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 @drpfenderson on GitHub (Feb 11, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/653
I just noticed that the old
index.jsonandindex.htmlthat were in my root archive directory have been renamed_old, but I'm not seeing a new version being output with my archive in the most recent 0.5.6 version. If I recall, theindex.jsonwas phased out in favor of the sqlite3 method. Has the static html been phased out for the server, or some other method, in the newer version? Is it perhaps hidden behind a flag or config option I'm missing?@ekiel commented on GitHub (Feb 11, 2021):
docker-compose run archivebox list --html --with-headers > index.htmlThis should work and I'm testing it now...
5:07 PM CST- it worked for me!
@drpfenderson commented on GitHub (Feb 11, 2021):
Asked and answered! Thanks a ton @ekiel
@pirate commented on GitHub (Feb 11, 2021):
We're pushing towards the server for security reasons. Static HTML is unfortunately very risky because replayed JS can make arbitrary requests to other files on your filesystem, including reading your whole index and all the other sites you've archived. The server aims to fix that by serving snapshot content with headers to lock down XSS/CSRF/CSP/etc.
You can still generate static html/json/csv main indexes with the
archivebox listcommand, but they'll no longer be automatically updated.However, the individual snapshot detail index pages are different, they're still static html and are still kept up-to-date in sync with the sqlitedb, unlike the main index which is now sqlite-only + optional static export.