mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #31] Add Support for Site Logins #21
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#21
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 @marlowe310 on GitHub (Jul 1, 2017).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/31
I'm trying to archive a few bookmarks that require I be logged in to the site itself for content to be visible -- which means BA is just outputting a page with the content concealed at this time.
Is there a way to log the chromium instance BA is using in, to prevent that from happening? Thanks much, very impressive work.
@pirate commented on GitHub (Jul 2, 2017):
Have you tried logging in to the sites using chrome normally before running the script? Headless chrome is just a command line interface to normal Chrome,
so it uses all the same cookies. Any sessions you log into via normal chrome should carry over in headless mode...Edit: it's not supported yetIf that doesn't work, there is another way but it's quite difficult. You run headless chrome with the remote debugging port open, then send custom JS commands (which depend on the structure of the site) to issue a POST request which logs you in. It's quite tricky to do, because you'd have to run the commands within the initial time window before chrome takes the screenshot.
@pirate commented on GitHub (Jul 6, 2017):
Closing this for now, but comment back if you're still having trouble and I'd be happy to re-open this and help out!
Added a note to the docs as well:
a7d1213@pirate commented on GitHub (Jul 22, 2017):
I stand corrected, apparently
chrome --headlessruns in incognito mode: https://bugs.chromium.org/p/chromium/issues/detail?id=617931@pirate commented on GitHub (Oct 30, 2017):
Done! https://github.com/pirate/bookmark-archiver/releases/tag/v0.0.3