When using the remote loader, it appears we get a content Length that is not accurate back from the server for multi-part content ranges for some assets. For example, using the SYSK podcast episode "Must We Suffer Emotional Pain?", the full file size is 55,581,968 bytes when downloaded. However, the remote loader is getting a byte size of 47,389,548, from the server content length which causes the buffer provider to think it is at the end of the file before it actually gets there.
We need a consistent way to get more accurate file sizes, or maybe just disable the multi-part requests?
This fix may also resolve #231 because it no longer is making partial requests. The entire file should just be available when first loaded from the secure source.
When using the remote loader, it appears we get a content Length that is not accurate back from the server for multi-part content ranges for some assets. For example, using the SYSK podcast episode "Must We Suffer Emotional Pain?", the full file size is 55,581,968 bytes when downloaded. However, the remote loader is getting a byte size of 47,389,548, from the server content length which causes the buffer provider to think it is at the end of the file before it actually gets there.
We need a consistent way to get more accurate file sizes, or maybe just disable the multi-part requests?