Ensure that request for first few bytes doesn't count as full download #13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When browser loads homepage, the counts shouldn't all shoot up
This is what apple podcasts does,
so it first does a probe with 0-1. Then it gets an MP3 frame and closes connection so that playback can start, and then it downloads the full file.
To solve these problems, I could send back smaller ranges even when the player requested longer ranges. But then buffering will take say 4 round trips instead of one upload burst. Or maybe some other solution. Instead of downloads maybe rename to "plays" and just count whenever someone requests the first 0 bytes. This usually happens only once usually. Can omit the 0-1 because the 0-1 is just to test whether range requests work