You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
❓ Question
Hello. I've come here from Prefect. In there, you can define the webhook URL into secret and use it in automations to notify users.
My question is in title. For example, when I have webhook for Mattermost like https://mattermost.example.com/hooks/yq6455fs7l7cu7fwmb9r3xs7dpn it would write 404 as It did not found but when I edit it so it looks more like mmosts://mattermost.example.com:443/yq6455fs7l7cu7fwmb9r3xs7dpn, it suddenly starts to work? This is absolute nonsense. Apprise should accept any kind of webhook format. If it already has the path for /hooks/ then don't edit that part. The same applies for the protocol. If it is already https then there's no need to parse it and in this case, throw error that the URL is unparsable. I don't know if the integration has been done by someone not really smart but this is horrible approach.
The text was updated successfully, but these errors were encountered:
Pheggas
changed the title
Why does webhook needs to have specific syntax in order apprise to take it?
Why does webhook needs to have specific syntax in order apprise to parse it?
Nov 21, 2024
❓ Question
Hello. I've come here from Prefect. In there, you can define the webhook URL into secret and use it in automations to notify users.
My question is in title. For example, when I have webhook for Mattermost like
https://mattermost.example.com/hooks/yq6455fs7l7cu7fwmb9r3xs7dpn
it would write 404 as It did not found but when I edit it so it looks more likemmosts://mattermost.example.com:443/yq6455fs7l7cu7fwmb9r3xs7dpn
, it suddenly starts to work? This is absolute nonsense. Apprise should accept any kind of webhook format. If it already has the path for /hooks/ then don't edit that part. The same applies for the protocol. If it is already https then there's no need to parse it and in this case, throw error that the URL is unparsable. I don't know if the integration has been done by someone not really smart but this is horrible approach.The text was updated successfully, but these errors were encountered: