Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Progress doesn't always work #9

Open
tcql opened this issue Mar 29, 2014 · 0 comments
Open

Progress doesn't always work #9

tcql opened this issue Mar 29, 2014 · 0 comments

Comments

@tcql
Copy link
Owner

tcql commented Mar 29, 2014

This is due to the fact that github generates zips on the fly when you download them. That means that content-length isn't known when a zip is generated. The reason that progress works sometimes is that recently downloaded archives are cached, and thus their content-length is known (so we know how much we are downloading, meaning progress works).

So far the only solution I've come up with to make them always work is to set up a server than hosts pre-downloaded archives. Downside is that the server has to be maintained (also paid for), and must be regularly checking for new updates/releases to stay up to date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant