Set User-Agent #1139
Labels
No labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
borgmatic-collective/borgmatic#1139
Loading…
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?
What I'd like to do and why
Nginx, when running within OPNSense, defaults to blocking "bad bots".
I have Healthchecks monitoring enabled (self-hosted) and
python-requests/2.31.0was seen when Borgmatic pinged my Healthchecks server. The connection was detected as being made by a "bad bot" and dropped. Perhaps it would not be a bad idea for Borgmatic to specify a custom User-Agent in requests to external systems? If nothing else it would not be blocked by any sort of "bad bot" detection as is done by a widely used routing and firewall software.As a bonus, it could act as advertising, making curious sysadmins aware of this fantastic tool (if they're not already aware of it)?
Other notes / implementation ideas
No response
Great idea! For now I've hard-coded "borgmatic" as the user agent on all outgoing requests. (Let me know if you need that to be customizable.)
This will be part of the next release.
Released in borgmatic 2.0.8!