<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p data-start="175" data-end="182">Hi all,</p>
<p data-start="184" data-end="411">I'm running an Icecast server
with HTTPS properly configured and working. Listeners can access
the streams securely via <code data-start="304" data-end="314">https://</code>,
and my mountpoints also specify the correct <code
data-start="360" data-end="370">https://</code> URLs using the <code
data-start="386" data-end="402"><http-headers></code>
section.</p>
<p data-start="413" data-end="712">However, the stream URL shown on
my station’s page at <a data-start="467" data-end="503" class=""
rel="noopener" target="_new" href="https://dir.xiph.org">dir.xiph.org</a>
still uses <code data-start="515" data-end="524">http://</code>
instead of <code data-start="536" data-end="546">https://</code>,
even though my server is only accessible via HTTPS. As a result,
my stream appears in the YP listings, but users can't actually
listen because the URL is incorrect.</p>
<p data-start="714" data-end="855">I have set the <code
data-start="729" data-end="736"><url></code> field in the
Icecast config to use <code data-start="772" data-end="782">https://</code>,
but that doesn't seem to affect the URL that the YP directory
receives.</p>
<p data-start="857" data-end="939">Is there a workaround or planned
fix for this? Is HTTPS YP support on the roadmap?</p>
<p data-start="941" data-end="987">Thanks in advance for your help,</p>
<p data-start="941" data-end="987">Marko<br>
</p>
<p></p>
</body>
</html>