Icecast - Jul 2019 - SSL-Question

thanks, that makes sense and works!
btw: is port 8443 sort of standard, which clients do consider?
bests, uno



Per Gunnarsson:
> I have one listening socket for http and one separate for https.
> 
> It looks like this:
> 
>   
>     <listen-socket>
>         <port>8000</port>
>     </listen-socket>
>  
> 
> 
>         <listen-socket>
>         <port>8443</port>
>         <ssl>1</ssl>
>         </listen-socket>
> 
> I don't think it's possible to have both encrypted and unencrypted
> traffic to the same port, but maybe somebody will correct me if that's
> possible.
> 
> Regards,
> 
> Per Gunnarsson
> On 2019-07-31 14:49, unosonic wrote:
> > hello,
> >
> >
> > I've icecast 2.4.4 /w SSL support, and when i enable SSL in the
config file:
> >
> > <ssl>1</ssl>
> > and
> > <ssl-certificate>my-all-inlusive.pem</ssl-certificate>
> >
> > I can connect via https://my-server:8000/my_stream
> > but only via https, no longer http. Is there an option to have both?
> > Also my source clients seems to be unableto connect anymore via http,
> > but have to look deeper into it.
> >
> > Any hints welcome. Sorry if this as covered already.
> >
> > thx, uno
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

Hi,

On 7/31/19 1:56 PM, unosonic wrote:
>
> thanks, that makes sense and works!
> btw: is port 8443 sort of standard, which clients do consider?

The RFC standardized ports for HTTP are:

80, alternatives: 8008, 8080

For HTTPS:

443

After all, Icecast is just another web server.

Please note the absence of 8000 and 8443. Neither are officially
specified for WWW type HTTP(S). They are commonly used as such, but 80
and 443 are *much* better choices and should be preferred.


Cheers,

TBR

> bests, uno
>
>
>
> Per Gunnarsson:
>> I have one listening socket for http and one separate for https.
>>
>> It looks like this:
>>
>>   
>>     <listen-socket>
>>         <port>8000</port>
>>     </listen-socket>
>>  
>>
>>
>>         <listen-socket>
>>         <port>8443</port>
>>         <ssl>1</ssl>
>>         </listen-socket>
>>
>> I don't think it's possible to have both encrypted and
unencrypted
>> traffic to the same port, but maybe somebody will correct me if
that's
>> possible.
>>
>> Regards,
>>
>> Per Gunnarsson
>> On 2019-07-31 14:49, unosonic wrote:
>>> hello,
>>>
>>>
>>> I've icecast 2.4.4 /w SSL support, and when i enable SSL in the
config file:
>>>
>>> <ssl>1</ssl>
>>> and
>>> <ssl-certificate>my-all-inlusive.pem</ssl-certificate>
>>>
>>> I can connect via https://my-server:8000/my_stream
>>> but only via https, no longer http. Is there an option to have
both?
>>> Also my source clients seems to be unableto connect anymore via
http,
>>> but have to look deeper into it.
>>>
>>> Any hints welcome. Sorry if this as covered already.
>>>
>>> thx, uno
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

Thomas B. Rücker:
> After all, Icecast is just another web server.
> 
> Please note the absence of 8000 and 8443. Neither are officially
> specified for WWW type HTTP(S). They are commonly used as such, but 80
> and 443 are *much* better choices and should be preferred.
makes sense, but if my webserver needs to serve http/s from the same IP,
that would not work. Unless I want to use Icecast as a nginx or apache 
replacement ;)