mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Custom HTTP_USER_AGENT/HTTP_REFERER per monitor #129
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#129
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 @RixzZ on GitHub (Aug 16, 2021).
Is it a duplicate question?
No.
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Allow to set a custom user-agent and referrer for each monitor.
In my use case I have an image CDN that filters image loading by referer. If you access it without a referer or not the correct one, you get redirected to the homepage.
Describe alternatives you've considered
Currently I can only use Uptime Kuma to test for a 302 (the redirection that happens when you fail the referer check), but I can't check any other condition.
Additional context
N/A
@louislam commented on GitHub (Aug 17, 2021):
I believe it is covered by #11.
@RixzZ commented on GitHub (Aug 17, 2021):
You're completely right. I searched for those specific headers, so I didn't fine that issue. Sorry.