mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1317] Feature Request: requests through proxy #3827
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#3827
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 @wirehack7 on GitHub (Jan 11, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1317
Type
What is the problem that your feature request solves
In some environments HTTP requests or even all outgoing requests have to go through a proxy. Or sometimes a proxy has to be used because of privacy reasons.
Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes
ArchiveBox client may do requests for archiving through a proxy when settings are set in config (wget, curl, chrome, etc)
What hacks or alternative solutions have you tried to solve the problem?
How badly do you want this new feature?
@pirate commented on GitHub (Jan 11, 2024):
Closing as duplicate of https://github.com/ArchiveBox/ArchiveBox/issues/249