HTTPS stream shown as HTTP in directory listing

Marko Jerak <[email protected]> Mon, 2 Jun 2025 17:36:43 +0200
Newsgroups gmane.comp.audio.icecast.general
Message-ID <[email protected]> 
This is a multi-part message in MIME format.
--===============1437051134520571329==
Content-Type: multipart/alternative;
 boundary="------------Cd3gc3rHxG8w6zaHZ0eDHIm9"
Content-Language: sl, en-US, hr, it, sl-SI

This is a multi-part message in MIME format.
--------------Cd3gc3rHxG8w6zaHZ0eDHIm9
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi all,

I'm running an Icecast server with HTTPS properly configured and 
working. Listeners can access the streams securely via |https://|, and 
my mountpoints also specify the correct |https://| URLs using the 
|<http-headers>| section.

However, the stream URL shown on my station’s page at dir.xiph.org 
<https://dir.xiph.org> still uses |http://| instead of |https://|, 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.

I have set the |<url>| field in the Icecast config to use |https://|, 
but that doesn't seem to affect the URL that the YP directory receives.

Is there a workaround or planned fix for this? Is HTTPS YP support on 
the roadmap?

Thanks in advance for your help,

Marko

--------------Cd3gc3rHxG8w6zaHZ0eDHIm9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!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">&lt;http-headers&gt;</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">&lt;url&gt;</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>

--------------Cd3gc3rHxG8w6zaHZ0eDHIm9--

--===============1437051134520571329==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Icecast mailing list
[email protected]
http://lists.xiph.org/mailman/listinfo/icecast

--===============1437051134520571329==--