You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually there are some points about HTTP/1.1 support (method SOURCE):
When Expect: 100-Continue provided Response code should be HTTP/1.1 100 Continue or one of error responses.
Currently:
HTTP/1.1 100 Continue
HTTP/1.0 200 OK
Then it accepts stream.
Status 200 OK (2xx) must be sent only when stream ends, stream should be sent after 100 Continue directly.
When Content-Length is not provided Transfer-Encoding should be chunked Transfer-Encoding: chunked
Currently: Icecast server accepts content without right headers and not chunked stream.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this!
Regarding the first issue, current master only sends HTTP/1.0 200 OK on the end of the stream, not right after the 100 Continue anymore.
Regarding the second, in master we have support for chunked transfer encoding and the source client can use that for PUT with Icecast 2.5. We will not enforce this though, for compatibility reasons.
Actually there are some points about HTTP/1.1 support (method SOURCE):
Expect: 100-Continue
provided Response code should beHTTP/1.1 100 Continue
or one of error responses.Currently:
Then it accepts stream.
Status 200 OK (2xx) must be sent only when stream ends, stream should be sent after 100 Continue directly.
Transfer-Encoding: chunked
Currently: Icecast server accepts content without right headers and not chunked stream.
The text was updated successfully, but these errors were encountered: