QMediaPlayer sends unnecesary http requests

Usually QMediaPlayer prefetches some metadata and then starts playing. 

For this is sends 2 http GET requests.

1. Regular request which is almost immediately closed
2. Ranged request (something starting with offset of ~20k)

It's all ok probably. But after connection is closed it sends another ranged request with boundries outside of file size.

for example I have a file on my server with size 123456 so next requests wil follow

1. regular GET (in my case in response I return Content-Length: 123456)
2. GET with "Range bytes=22720-" header (in response we return Content-Range: 0-123455/123456)
3. GET with "Range bytes=123456-"

This last request doesn't make sense. QMediaPlayer was already told about actual file size. There is no reason to check anything outside of this limit. Instead if the file supposed to be changed during download on server side, server app should not return file's size aywhere.