id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
12444	/Content/GetRecording sets partial Content-Length when serving unfinishing recordings	ajb@…	stuartm	"Hi,
  I'm trying to do chase-play on an unfinished recording using the SmartMythTV app on a Samsung smart tv. When the client requests an as yet incomplete recording, the response includes Content-Length and Content-Range headers with the current size of the file. The player always stops before the end of the program although the recording has completed in the meantime. I suspect the client is obeying the indicated length of the data rather than reading until hitting EOF.

Normal recording                                                           
{{{
GET /Content/GetRecording?ChanId=3004&StartTime=2015-05-03T15:00:00Z HTTP/1.1
User-Agent: Lavf52.104.0
Accept: */*
Range: bytes=0-
Connection: close
Host: 192.168.3.45:6544
                                                                                
HTTP/1.1 206 Partial Content
Date: 3 May 2015 16:48:26
Server: Linux 3.13.0-49-generic, UPnP/1.0, MythTV 0.27.20141016-1
Accept-Ranges: bytes
Cache-Control: no-cache=""Ext"", max-age = 5000
Content-Range: bytes 0-1108512483/1108512484
Connection: Close
Content-Type: video/mpeg
Content-Length: 1108512484
}}}

Unfinished recording I want to chase play
{{{

GET /Content/GetRecording?ChanId=3001&StartTime=2015-05-03T16:52:00Z HTTP/1.1
User-Agent: Lavf52.104.0
Accept: */*
Range: bytes=0-
Connection: close
Host: 192.168.3.45:6544
                                                                                
HTTP/1.1 206 Partial Content
Date: 3 May 2015 16:52:27
Server: Linux 3.13.0-49-generic, UPnP/1.0, MythTV 0.27.20141016-1
Accept-Ranges: bytes
Cache-Control: no-cache=""Ext"", max-age = 5000
Content-Range: bytes 0-14843351/14843352
Connection: Close
Content-Type: video/mpeg
Content-Length: 14843352
}}}

As you can see there's no difference in the type of headers sent between the complete and the incomplete recording. I'm thinking that if the Content-Range and the Content-Length were not present the Smart TV player would continue until the EOF. Is that a reasonable assumption, or does HTTP 1.1 mandate them?

Thanks,


Andrew"	Bug Report - General	closed	major	0.28.2	MythTV - Services API - Backend	0.27-fixes	medium	Won't Fix	Content-Length Chase-Play		0