[GH-ISSUE #653] Question: Does Archivebox 0.5.6 still output static index.html? #411

Closed
opened 2026-03-01 14:43:18 +03:00 by kerem · 3 comments
Owner

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.json and index.html that 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, the index.json was 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?

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.json` and `index.html` that 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, the `index.json` was 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?
kerem closed this issue 2026-03-01 14:43:19 +03:00
Author
Owner

@ekiel commented on GitHub (Feb 11, 2021):

docker-compose run archivebox list --html --with-headers > index.html

This should work and I'm testing it now...

5:07 PM CST- it worked for me!

<!-- gh-comment-id:777851673 --> @ekiel commented on GitHub (Feb 11, 2021): `docker-compose run archivebox list --html --with-headers > index.html` This should work and I'm testing it now... 5:07 PM CST- it worked for me!
Author
Owner

@drpfenderson commented on GitHub (Feb 11, 2021):

Asked and answered! Thanks a ton @ekiel

<!-- gh-comment-id:777868686 --> @drpfenderson commented on GitHub (Feb 11, 2021): Asked and answered! Thanks a ton @ekiel
Author
Owner

@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 list command, 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.

docker-compose run archivebox list --html --with-headers > index.html
docker-compose run archivebox list --json --with-headers > index.json
docker-compose run archivebox list --csv > index.csv
<!-- gh-comment-id:777872999 --> @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 list` command, 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. ```bash docker-compose run archivebox list --html --with-headers > index.html docker-compose run archivebox list --json --with-headers > index.json docker-compose run archivebox list --csv > index.csv ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ArchiveBox#411
No description provided.