[duplicate] icecast sends output of <on-connect> script to source client
Please look at #2087 (closed) instead.
Using the on-connect script from #2087 (closed), a client which does not close the connection immediately after receiving the 200 response, has a chance of reading “stdout” after stopping to send any data.
If this is unintentional, this data should end up in e.g. the <errorlog>
target.
If this is intentional, the length of the data should be indicated by a Content-Length
header, or should be properly encoded as Transfer-Encoding: chunked
(which would then be required as a header in the response).