bpa

I only used started using HTTP 1.1 for HLS via a plugin lib module to have persistent connections. Philippe implemented fully within LMS possibly for UPNP or bridge stuff. HTTP...

Not clear what point the AnyEvent::HTTP comment is addressing. Referring to initial comment - I think any HLS (i.e.m3u8) or DASH stream will expect to use HTTP 1.1 - HLS/DASH...

Looking though LMS code - I think all the chunked support is as LMS as a recipient of a request (e.g. a JSONRPC or a UPNP request) requiring chunked encoding....

From what I read the discussion about TheCheese, the issue about not supporting HTTP 1.0 seemed to be tied into TLS 1.0 and 1.1 but disabling HTTP 1.0 is collateral...

For completeness. I have a dev version of PlayHLS which supports fMP4/Flac and uses internal LMS HTTP 1.1 support unlike PlayHLS 2.* . On LMS 8.5.2 and the dev plugin...

LMS does an initial HTTP1.0 GET of the m3u8 file before handling over the PlayHLS based on MIME/suffix returned - if that initial GET is blocked then stream can't play...

Looking further into HTTP/1.1 and chunked encoding. AFAICT LMS does not use AnyEvent::HTTP - so any handling of chunked data is within LMS routines. There are two places where HTTP/1.0...