Using latest Icecast kh13 I've found an issue with HAProxy as load-balancer/HTTP processor (I use this combo to add to Icecast extra features such as GeoIP filtering, relay fallback, HTTPS terminator, JWT authentication, SHOUTCast to Icecast2 URL converter... very useful, happy with this combo)
So far, everything is perfect..... but as logn as a single mountpoint is on Icecast side.
On HAProxy config side, I'm using keep-alive and cookie to preserve connection between listener and icecast as far I'm able to ... So far, it works perfect... until two mountpoints.
The combo, even with two mountpoints, still works with desktop players such as VLC, or video web-based players... but fails when using plain HTML5 or just pointing a browser to the URL
For reasons I don't know, the connection is closed... What could be happening? why does it work when single mountpoint? Is there any noticeable difference on the HTTP connection when single or multiple mountpoints do exist?
Hi community.
Using latest Icecast kh13 I've found an issue with HAProxy as load-balancer/HTTP processor (I use this combo to add to Icecast extra features such as GeoIP filtering, relay fallback, HTTPS terminator, JWT authentication, SHOUTCast to Icecast2 URL converter... very useful, happy with this combo)
So far, everything is perfect..... but as logn as a single mountpoint is on Icecast side. On HAProxy config side, I'm using keep-alive and cookie to preserve connection between listener and icecast as far I'm able to ... So far, it works perfect... until two mountpoints.
The combo, even with two mountpoints, still works with desktop players such as VLC, or video web-based players... but fails when using plain HTML5 or just pointing a browser to the URL
For reasons I don't know, the connection is closed... What could be happening? why does it work when single mountpoint? Is there any noticeable difference on the HTTP connection when single or multiple mountpoints do exist?
Regards.