Open trilliot opened 6 years ago
Hello Karl, I saw you were planning to release a new version.
Any news on this? Have you been able to reproduce, or is there something incorrect in my config? I will try to reproduce on kh10 today.
~Could not reproduce with kh10 nor kh8.~ ~Sorry for the noise, I will try to figure out what's happening on my side.~
I managed to reproduce on kh10, see below.
Hi again,
I finally found what's happening. The issue is still here with kh10, but it's quite tricky.
The timelimit header is properly handled when the listener uses Firefox as browser (that is now my primary browser, explains why I first though the issue was fixed). However, if you listen to the stream with Chrome (or Chromium or any derivative), the timelimit auth is not taken into account.
See attached screenshot from my test VM (Centos 7, fresh kh10 build):
The first listener (using Firefox) is kicked after about 10 seconds, however the second listener (using Chromium) is not.
I confirm this issue on icecast-2.4.0-kh10 not working with latest version of both firefox and chrome. It worked well on icecast-2.3.3-kh10
Expected behavior: Stream should drop authenticated listener in 10 to 15 seconds What happens: Authenticated Listener continues on the stream until manually stopped.
My php auth script <?php header("icecast-auth-timelimit: 10"); header("icecast-auth-user: 1");
it is down to the use of range headers conflicting with the timelimit setting. I have verified a fix here locally, should be in master shortly ready for a kh11 build.
karl.
Hello,
I'm using the kh8 build (not migrated to kh9 yet because of various issues pointing instabilities). I'm facing an issue with the timelimit header, that seems not taken into account.
Update: tried on kh10, still exists. See https://github.com/karlheyes/icecast-kh/issues/223#issuecomment-438223570
Here is my configuration:
I wrote a simple auth server in Python 2 that replies with
icecast-auth-user: 1
andicecast-auth-timelimit: 10
headers to every POST request:But when I listen to the
/test
mountpoint, icecast doesn't take the 10 seconds into account and never drops the connection.You can check that the server is properly returning headers by curling it:
Am I missing something?