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
The SwitchBot backend seems to sanitize the protocol on registered webhook URLs irregularily. This might be indicative of a deeper issue, maybe security relevant.
Expected Behavior
Protocol should always or never be taken into account for webhooks.
Steps To Reproduce
register a webhook with https https://example.org/webhook
try registering another webhook without https http://example.org/webhook -> error message webhook is exist
attempt deletion of existing https webhook but using the http url http://example.org/webhook -> gives a success message
attempt registering http://example.org/webhook again -> failure, because 3) did not actually delete the webhook, even though it gave a success message
delete https://example.org/webhook
you are now able to register http://example.org/webhook
This means the system is only SOMETIMES treating http://example.org/webhook and https://example.org/webhook as the same URL.
Logs
n/a
Configuration
n/a
Environment
REST api
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Analysis
The SwitchBot backend seems to sanitize the protocol on registered webhook URLs irregularily. This might be indicative of a deeper issue, maybe security relevant.
Expected Behavior
Protocol should always or never be taken into account for webhooks.
Steps To Reproduce
https://example.org/webhook
http://example.org/webhook
-> error messagewebhook is exist
http://example.org/webhook
-> gives a success messagehttp://example.org/webhook
again -> failure, because 3) did not actually delete the webhook, even though it gave a success messagehttps://example.org/webhook
http://example.org/webhook
This means the system is only SOMETIMES treating
http://example.org/webhook
andhttps://example.org/webhook
as the same URL.Logs
Configuration
n/a
Environment
REST api
Additional Context
No response
The text was updated successfully, but these errors were encountered: