Bug #3207
Failure when receiving HTTP/1.1 answer on HTTP/1.0 request
100%
Description
I managed to find why the download of the M3U playlist for Freebox TV fails. Its public URI is http://mafreebox.freebox.fr/freeboxtv/playlist.m3u (normally, mafreebox.freebox.fr resolves to a non-routable IP, except for Free.fr ISP subscribers).
However, the server answer to it with a "302 Moved Temporarily" using HTTP/1.0, and TVH re-use this header to follow the new URI (in my case it is http://212.27.40.238/pub/playlist.m3u). But the server of this new URI is using HTTP/1.1, whatever the type of the request. It may be a bug from the server itself, but I don't know if its written somewhere in an RFC or not.
Moreover, since the original request is done using HTTP/1.1, shouldn't it be used all over the redirections?
History
Updated by Jaroslav Kysela about 9 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:tvheadend|ae1f1235810a24434422412ac46b59fcf07d21a0.
Updated by Adrien CLERC about 9 years ago
I confirm this change fixes my issue. Many thanks for that.