Answer blocked host names like unreachable ones

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 402ad0a03a
commit 62141c0840
6 files changed
+121 -20

No files matched your search

+5
View File
@@ -140,6 +140,11 @@ 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.
"Address not allowed" is only said for what the URL itself shows (scheme,
credentials, port, an IP address). A host name that resolves to a blocked
address gets the same answer as a name that does not resolve or a server that
does not answer ("could not connect"), so users cannot find out which names
exist in the server's internal DNS.
Episode audio is streamed by the browser directly from the publisher. Some
publishers cannot be played that way (plain HTTP while this server uses