-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
saveStatusPage
socket handler does not use icon
specified in payload if not base64-encoded
#4749
Comments
Yes that is a bug. |
I have a PR almost ready, I'm just currently confirming on my patched local that it's possible to use the URL variant at all. Assuming I can work out some CORS issues, then I'm expecting I can provide a simple one-liner. As to how I came across it: I am automating a from-scratch status page setup, so the UI-driven upload flow is a no-go for me. I also don't really like the base64 upload because then I have to pull the current image and check if the contents match since I want to report whether I am changing the icon. I'd rather use either a cross-origin URL or a path relative to the data volume (I'm using the docker deployment variant). |
I don't care about the attribution though; this is not my personal account |
Confirmed that things work fine if I do this simple fix: #4750 |
📑 I have found these related issues/pull requests
I did not find any related issues
🛡️ Security Policy
Description
uptime-kuma/server/socket-handlers/status-page-socket-handler.js
Lines 139 to 157 in dbbc79a
config.icon
is never again referenced, onlyconfig.logo
👟 Reproduction steps
write to the status page socket handler with a payload like:
or similar.
👀 Expected behavior
Status page should use provided icon.
😓 Actual Behavior
Status page keeps using whatever icon it is already using
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
Debian bookworm aarch64
🌐 Browser
Google Chrome 124.0.6367.119
🖥️ Deployment Environment
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: