mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #864] Bug: URLs with parentheses are mishandled by archivebox add #3554
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#3554
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 @WesleyAC on GitHub (Sep 28, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/864
Describe the bug
URLs like
https://en.wikipedia.org/wiki/APL_(programming_language)are silently converted tohttps://en.wikipedia.org/wiki/APL_.Steps to reproduce
archivebox initecho "https://en.wikipedia.org/wiki/APL_(programming_language)" | archivebox addORarchivebox add "https://en.wikipedia.org/wiki/APL_(programming_language)"archivebox listnow showshttps://en.wikipedia.org/wiki/APL_ "APL - Wikipedia", which is incorrect.ArchiveBox version
@WesleyAC commented on GitHub (Sep 28, 2021):
Looks like this is related to #235 / #287, but since those are closed, I think it makes sense to file this.
@WesleyAC commented on GitHub (Sep 28, 2021):
Oh, I see — I need to manually give it the
--parseroption. Could that be mentioned somewhere more visible in the docs? Maybe in the input formats section of the readme?@WesleyAC commented on GitHub (Sep 28, 2021):
Specifically, it'd be great to have an example like: