Keep network details and URLs out of podcast fetch errors

Users see the kind of failure only; resolved addresses and transport
details go to the logs, without URLs. Feed and audio requests are
limited to the web ports.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
sanapachandClaude Opus 5.5 committed 2026-11-20 15:12:38 +02:00
1 parent 99b2935b35
commit c51a9af9e5
10 files changed
+256 -42

No files matched your search

+7 -4
View File
@@ -123,10 +123,13 @@ feed metadata only, never episode audio. A failing feed keeps its known
episodes. Accounts subscribed to the same feed share one request.
The server therefore makes outgoing HTTP(S) requests to podcast publishers.
It only connects to public addresses: feed or audio URLs that point to
loopback, private, link-local, CGNAT or cloud metadata addresses, directly,
through DNS or through a redirect, are refused. System proxy settings are not
used for these requests.
It only connects to public addresses on the web ports 80, 443, 8080 and 8443:
feed or audio URLs that point to loopback, private, link-local, CGNAT or cloud
metadata addresses, directly, through DNS or through a redirect, or to any
other port, are refused. System proxy settings are not used for these
requests. Users only see the kind of failure (address not allowed, could not
connect, HTTP status, not a feed); the details, without the URL, are in the
server log and, for scheduled refreshes, in the job log with the podcast id.
Episode audio is streamed by the browser directly from the publisher. Some
publishers cannot be played that way (plain HTTP while this server uses