Hi! I've been giving support for streaming and streamcasting over HTTPS... Everything started while giving streaming support to my website. When I read a console error (or was it a warning?) on Chrome, when the browser accessed to an http:// resource from an https:// domain. Then I decided to fix it by the clean way. I don't need official support yet... but if you don't mind to give full HTTPS support I can help you I think, because [...] very easy to fix, and so. If you want, I want share my patch. I did not give full support (for example in configuration). Also, the xiph directory needs http:// scheme always... so your help would be nice.
Hi Abel, I'm not quite sure I understand your predicament here. We settled for using our main nginx with proxy_buffering off for the media files. That way certbot takes care of it too. Regards On Wed, 13 Mar 2019 at 13:36, Abel Romero <romeroperezabel at gmail.com> wrote:> > Hi! > > I've been giving support for streaming and streamcasting over HTTPS... > > Everything started while giving streaming support to my website. When I > read a console error (or was it a warning?) on Chrome, when the browser > accessed to an http:// resource from an https:// domain. > > Then I decided to fix it by the clean way. > > I don't need official support yet... but if you don't mind to give full > HTTPS support I can help you I think, because [...] very easy to fix, > and so. > > If you want, I want share my patch. > > I did not give full support (for example in configuration). > > Also, the xiph directory needs http:// scheme always... so your help > would be nice. > > > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev
Good afternoon, On Wed, 2019-03-13 at 17:35 +0100, Abel Romero wrote:> Hi! > > I've been giving support for streaming and streamcasting over HTTPS... > > Everything started while giving streaming support to my website. When I > read a console error (or was it a warning?) on Chrome, when the browser > accessed to an http:// resource from an https:// domain. > > Then I decided to fix it by the clean way. > > I don't need official support yet... but if you don't mind to give full > HTTPS support I can help you I think, because [...] very easy to fix, > and so. > > If you want, I want share my patch. > > I did not give full support (for example in configuration).I'm not exactly sure what this is about. Icecast supports TLS for a very very long time already. Plus Icecast 2.4.x and Icecast 2.5.x also did a number of improvements to this.> Also, the xiph directory needs http:// scheme always... so your help > would be nice.This is true. Marvin Scholz is working on that. Maybe he want to give us an update? With best regards, -- Philipp Schafft (CEO/Geschäftsführer) Telephon: +49.3535 490 17 92 Löwenfelsen UG (haftungsbeschränkt) Registration number: Bickinger Straße 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20190315/a4fecbe9/attachment.sig>
Sorry, I sent it individually. Didn't I? ---------- Forwarded message --------- From: Abel Romero <romeroperezabel at gmail.com> Date: Wed, Mar 13, 2019, 6:19 PM Subject: Re: [Icecast-dev] Full HTTPS support To: <listas at tangopardo.com.ar> Oh, that's a good solution! My predicament is complicated to explain :- ) The only I want to share is a full HTTPS solution for icecast-server... El 13/03/2019 a las 17:47, Adrian Pardini escribió:> Hi Abel, I'm not quite sure I understand your predicament here. > > We settled for using our main nginx with proxy_buffering off for the > media files. That way certbot takes care of it too. > > Regards > > On Wed, 13 Mar 2019 at 13:36, Abel Romero <romeroperezabel at gmail.com>wrote:>> Hi! >> >> I've been giving support for streaming and streamcasting over HTTPS... >> >> Everything started while giving streaming support to my website. When I >> read a console error (or was it a warning?) on Chrome, when the browser >> accessed to an http:// resource from an https:// domain. >> >> Then I decided to fix it by the clean way. >> >> I don't need official support yet... but if you don't mind to give full >> HTTPS support I can help you I think, because [...] very easy to fix, >> and so. >> >> If you want, I want share my patch. >> >> I did not give full support (for example in configuration). >> >> Also, the xiph directory needs http:// scheme always... so your help >> would be nice. >> >> >> _______________________________________________ >> Icecast-dev mailing list >> Icecast-dev at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast-dev > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20190316/d8224ce1/attachment.html>
Same... ---------- Forwarded message --------- From: Abel <romeroperezabel at gmail.com> Date: Fri, Mar 15, 2019, 2:38 PM Subject: Re: [Icecast-dev] Full HTTPS support To: Philipp Schafft <phschafft at de.loewenfelsen.net> Good afternoon, can you send audio as source over HTTPS? Also, can you use Icecast to generate .m3u, etc files with the https URL? And finally nice to see you are working on xiph directory. On Fri, Mar 15, 2019, 2:31 PM Philipp Schafft <phschafft at de.loewenfelsen.net> wrote:> Good afternoon, > > On Wed, 2019-03-13 at 17:35 +0100, Abel Romero wrote: > > Hi! > > > > I've been giving support for streaming and streamcasting over HTTPS... > > > > Everything started while giving streaming support to my website. When I > > read a console error (or was it a warning?) on Chrome, when the browser > > accessed to an http:// resource from an https:// domain. > > > > Then I decided to fix it by the clean way. > > > > I don't need official support yet... but if you don't mind to give full > > HTTPS support I can help you I think, because [...] very easy to fix, > > and so. > > > > If you want, I want share my patch. > > > > I did not give full support (for example in configuration). > > I'm not exactly sure what this is about. > Icecast supports TLS for a very very long time already. Plus Icecast > 2.4.x and Icecast 2.5.x also did a number of improvements to this. > > > > Also, the xiph directory needs http:// scheme always... so your help > > would be nice. > > This is true. Marvin Scholz is working on that. Maybe he want to give us > an update? > > With best regards, > > -- > Philipp Schafft (CEO/Geschäftsführer) > Telephon: +49.3535 490 17 92 > > Löwenfelsen UG (haftungsbeschränkt) Registration number: > Bickinger Straße 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > -----BEGIN PGP SIGNATURE----- > Comment: Because it's your freedom > > iQEcBAABCAAGBQJci6lBAAoJEMuUk2IbcLLbTl8H/RwSmKNz/Uyx0QjGDCX65eSM > VAIGyqsAeZtjVevhXOhV+xCFuth4gQdpM5QZVoUnOHMb+cs3CGI3XNGI1TULPwqu > hZKhLvMK6YKt3Ge7zFRGjzYPvSrLK1MofZa/KSTpibIxZ9P/oSoWyGjKLp7DDnF0 > /VAClPhB5sncBfUY4paQoh18JfPlKwBXH8qiXj25UAIHR7RsWBl7+5QKg6J+S7jy > oJy+OLS+b46dGmVoeYTvdAvLnHHlsE0cxB+0pVBqPwc+lA30baceRO5Ax31vw2nh > 2deoUYtOKTqre0sdrPMKPqEvdBcT8F5EOZnctRsvd8rKTC2/UYhSxRiY7UrCEvY> =G2xA > -----END PGP SIGNATURE----- >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20190316/b3faeb34/attachment.html>
Sorry, my smartphone client was replying individually. I attach my last message On Wed, Mar 13, 2019, 5:47 PM Adrian Pardini <listas at tangopardo.com.ar> wrote:> Hi Abel, I'm not quite sure I understand your predicament here. > > We settled for using our main nginx with proxy_buffering off for the > media files. That way certbot takes care of it too. > > Regards > > On Wed, 13 Mar 2019 at 13:36, Abel Romero <romeroperezabel at gmail.com> > wrote: > > > > Hi! > > > > I've been giving support for streaming and streamcasting over HTTPS... > > > > Everything started while giving streaming support to my website. When I > > read a console error (or was it a warning?) on Chrome, when the browser > > accessed to an http:// resource from an https:// domain. > > > > Then I decided to fix it by the clean way. > > > > I don't need official support yet... but if you don't mind to give full > > HTTPS support I can help you I think, because [...] very easy to fix, > > and so. > > > > If you want, I want share my patch. > > > > I did not give full support (for example in configuration). > > > > Also, the xiph directory needs http:// scheme always... so your help > > would be nice. > > > > > > _______________________________________________ > > Icecast-dev mailing list > > Icecast-dev at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast-dev > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20190316/25c13873/attachment.html>