mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #129] Value of WGET_USER_AGENT not quoted correctly #3106
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#3106
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 @sbrl on GitHub (Jan 12, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/129
Describe the bug
A clear and concise description of what the bug is.
I've noticed that the value of the
WGET_USER_AGENTenvironment variable is not properly quoted by ArchiveBox. For example, I'm setting it to this in bash:This should result in something like
ArchiveBox/7890abc (+https://github.com/pirate/ArchiveBox/) wget/1.18. The above causes a bogus 404 Not Found error on every request. However, changing it to this:....solves the issue.
Expected behavior
A clear and concise description of what you expected to happen.
I shouldn't have to add the quotes manually myself in the
WGET_USER_AGENTenvironment variableScreenshots
If applicable, add screenshots to help explain your problem.
Here it is not working:
Here it is with the workaround:
Desktop (please complete the following information):
33942d37cbSmartphone (please complete the following information):
Additional context
Add any other context about the problem here.
@pirate commented on GitHub (Jan 12, 2019):
Thanks for the beautiful bug report! Fixed in
b77476c, let me know if you're still having trouble and I'll re-open it.@sbrl commented on GitHub (Jan 12, 2019):
Yep - looks like that did the trick. Thanks! :D