HTTP request header 'Accept-Ranges' does does not respond in some case

From @border0464111 on Tue Aug 02 2016 18:01:29 GMT+0000 (UTC)

I was trying to embed some video and in a webpage, They work well if I call them directly but not working once imbeded if they are not on my local cache.

So I narrowed the problem to a point where the following query (wich replicate query made by my webpage) will never receive a response and hang eternaly:

curl ‘,%20NCS,%20Dubstep-iJ05N8pCI0E.webm’ -H ‘Referer:’ -H ‘Accept-Encoding: identity;q=1, *;q=0’ -H ‘User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/51.0.2704.79 Chrome/51.0.2704.79 Safari/537.36’ -H ‘Range: bytes=390496256-’ --compressed

If I change to ‘Range: bytes=9000-’ or remove it completely. The data will start to flow in.

Im supposing file lenght is smaller then 390496256. ( But due to an other bug, Im sudently unable to resolve de IPNS anymore… )

In any case, what ever is the reason for this. Gateway should return HTTP 416 status code(Requested Range Not Satisfiable) instead of hanging.

Copied from original issue:

From @border0464111 on Tue Aug 02 2016 18:04:44 GMT+0000 (UTC)

After futher reading, The attempt of my browser to query chunks over the file size could be caused by gzip compression of playable formats. Wich would open an other issue.