[KallanX]

Summary

HTTP notification settings were saved, and the test button delivered them, but a new episode never did. The refresh path only knew how to send ntfy and Gotify. An enabled HTTP channel was loaded as an unknown platform and dropped, which logged Unknown notification platform: http.

New episodes now post to the saved HTTP webhook.

What changed

• load_notification_targets in rust-api/src/database.rs now reads httpurl, httptoken, and httpmethod on both Postgres and MariaDB/MySQL.
• send_new_episode_notifications handles the http platform. POST sends JSON. GET puts the notice in a message query parameter. A non-empty token is sent as Authorization: Bearer …, except for Telegram URLs, which keep the test sender's chat_id behavior.
• The webhook URL is not logged, because Mattermost and similar hooks embed a secret in the path.
• The integration fixture server records request bodies so the test can check the payload.

POST body:

{
  "title": "New Podcast Episode",
  "message": "New episode available for Show Name: Episode Title",
  "text": "New episode available for Show Name: Episode Title"
}

[madeofpendletonwool]

Made similar adjustments recently to fix this as well. I'm adjusting your commit to keep the extra tests and merging so that you get the credit.