In version 2.4.0-kh17 the handling of HTTP response headers was changed. This was done to allow for custom headers to be injected via the xml http-headers block.
However, it appears that this broke the setting of the Server header.
Before, icecast would respond with something like this:
Server: Icecast 2.4.0-kh15
Since kh17, the server responds with this:
Server: Icecast
Also, before kh17 it used to be possible to use something like this in the config file:
<server-id>Foo</server-id which would result in the server responding with Server: Foo
Now setting a specific Server header can be done post kh17, using a http-headers block:
However, this does not allow for the automatic injection of the running version (e.g. 2.4.0-kh17) in the Server header.
Attached is a very simpleminded patch against kh22 to include the running version in the Server header. However, this does not do anything in regard to <server-id>
In version 2.4.0-kh17 the handling of HTTP response headers was changed. This was done to allow for custom headers to be injected via the xml
http-headers
block. However, it appears that this broke the setting of the Server header. Before, icecast would respond with something like this:Server: Icecast 2.4.0-kh15
Since kh17, the server responds with this:Server: Icecast
Also, before kh17 it used to be possible to use something like this in the config file:
<server-id>Foo</server-id
which would result in the server responding withServer: Foo
Now setting a specific Server header can be done post kh17, using a
http-headers
block:However, this does not allow for the automatic injection of the running version (e.g.
2.4.0-kh17
) in the Server header. Attached is a very simpleminded patch against kh22 to include the running version in the Server header. However, this does not do anything in regard to<server-id>
Regards, Dick.