Tvheadend

Adam Sutton wrote:

Not able to repeat this myself. Please try curl -I URL, to shows the headers sent for one of the faulty recordings URLs.

Adam

Thx

Maybe something with filenames? I have "remove unsafe..." checked.

Here is your output (i had to use "curl -I --user name:psw page"):

A file that works:

dertester@tv:~$ curl -I --user dertester:secret:P http://tv:9981/dvrfile/154
HTTP/1.1 200 OK
Server: HTS/tvheadend
Last-Modified: Mon, 9 Jun 2014 18:33:37 GMT
Expires: Mon, 9 Jun 2014 18:33:47 GMT
Cache-Control: max-age=10
Connection: Keep-Alive
Content-Type: video/x-matroska
Content-Length: 1568893145
Content-Disposition: attachment; filename=Tatort:_Nasse_Sachen.mkv

A file that gives me double headers:

dertester@tv:~$ curl -I --user dertester:secret:P http://tv:9981/dvrfile/123
HTTP/1.1 200 OK
Server: HTS/tvheadend
Last-Modified: Mon, 9 Jun 2014 18:37:43 GMT
Expires: Mon, 9 Jun 2014 18:37:53 GMT
Cache-Control: max-age=10
Connection: Keep-Alive
Content-Type: video/x-matroska
Content-Length: 1442753972
Content-Disposition: attachment; filename=Gute_Zeiten,_schlechte_Zeiten.mkv

Ps changed version:
Ubuntu 13.10, 32bit (3.11.0-23-generic)
HTS Tvheadend 3.9.788~g385c190~saucy

If i can give you more info, pls tell me

Maybe something with filenames? I have "remove unsafe..." checked.

it seems to be connected to the "," character in the recording. I created a test recording with it and cant download in chrome.

Hope that helps

The only solution to this is to sanitize the name of the entry before serving it to the browser, regardless of the setting which controls this normally.