|
i didn't reference user-agents in my reply so not sure where that has come from.
the changes i mentioned in v2.2 are based on looking at the request url (not the user-agent) so it is able to drop sending it as long as that part is found from the client request be it from the shoutcast.com player (which is what it was designed for) or a 3rd party option.
so yes, it should resolve the issue with stream playback issues if someone uses the shoutcast.com player if using a v2.2 DNAS to provide the stream.
|