does icecast force ssl if enabled?

does icecast force ssl if enabled?



In the documentation for icecast 2.4.2 I see the following about ssl.



ssl If set to 1 will enable HTTPS on this listen-socket. Icecast must
have been compiled against openSSL to be able to do so.



However this wording is unclear to me whether or not the ssl is forced for this port or not? I am wondering this because we are running into an issue where safari is forcing ssl redirect and we want to keep the server listening on both ssl and non-ssl on the same port ( if thats possible )



Another thing is that it says it must be compiled against openSSL but we are installing it from apt in xenial. Does this mean its default to ssl?


apt


xenial



Thanks~!






I'm not sure what you mean by "forced".

– TBR
Sep 17 '18 at 15:22






Will all traffic be redirected to ssl?

– Pablo Marti Cordero
Sep 17 '18 at 15:26






Please note that the default Ubuntu packages (as they descend from Debian) are built without openSSL. How to get a version that is compiled against openSSL on Debian or Ubuntu? Use the official Xiph.org Icecast packages.

– TBR
Sep 25 '18 at 8:23





2 Answers
2



However this wording is unclear to me whether or not the ssl is forced for this port or not?



On that particular socket, it is. A server bound to that socket cannot support HTTPS and non-HTTPS at the same time. Usually, you'll use port 80 for HTTP and port 443 for HTTPS.


80


443



Note that you can have multiple sockets bound to Icecast, simply by putting in multiple <listen-socket> sections. It's common to serve both HTTP and HTTPS this way.


<listen-socket>



I am wondering this because we are running into an issue where safari is forcing ssl redirect



Your server configuration is irrelevant here. Icecast will not redirect HTTP requests to HTTPS. It's possible that you hit the stream on HTTPS once and that Safari cached this. It's also possible that you turned on HSTS or something for your domain. You would have to debug this with a tool like Fiddler.



and we want to keep the server listening on both ssl and non-ssl on the same port



You say "keep the server listening"... that's not possible. If it appears you're set up this way today, that's not accurate.



In a sense it does. Icecast if you are using it as its own server will not resolve the enabled ssl port unless its https://.


https://



You also cannot use the same port for both ssl and non-ssl.



Finally the xenial ubuntu package also is not compiled for ssl.



Thanks for contributing an answer to Stack Overflow!



But avoid



To learn more, see our tips on writing great answers.



Required, but never shown



Required, but never shown




By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Popular posts from this blog

𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

Edmonton

Crossroads (UK TV series)