Open romano opened 3 weeks ago
Hello,
I don't have a Gotify server to check, but I think it's normal the headers are not sent with the /health request, I think this endpoint is public and does not requires the auth token.
How did you managed to allow CORS? directly in Gotify? It could be a bug in Gotify where headers are not sent on the health endpoint. You could try to confirm that by performing a curl request to check the headers, something like curl -I <your-gotify-url>/health
Describe the bug "http://gotify.server.local/health" reports missing CORS header "Access-Control-Allow-Origin". I've managed to allow CORS in Gotify. The service reads message counts but fails to read Gotify's health status.
This bit (lines 54-67) seems to push headers only for messages, but not the health requests. Could be an easy fix but haven't tested it.
As a side note this bit (lines 41-47) returns green health regardless if it achieves connection. Should probably return red by default.
Expected behavior No errors
Logs & errors
Browser console output:
Screenshots n/a
Configuration n/a