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

Handling of client disconnects #82

Open
mecampbellsoup opened this issue Mar 19, 2021 · 2 comments
Open

Handling of client disconnects #82

mecampbellsoup opened this issue Mar 19, 2021 · 2 comments

Comments

@mecampbellsoup
Copy link

Hey @evanmiller! Hope you are doing well man. mod_zip is generally working great for us :)

I have a question that may or may not be related to mod_zip specifically.

In short, in our application we stream large (10+ GB) file/directory downloads to our users. Often times they are in places with unreliable internet connections. It seems that when there is some service interruption, these long-running downloads get interrupted and cannot resume where they left off.

Could we use Last-Modified to pick up where the download left off?

To save bandwidth, add a "Last-Modified" header in the upstream response; mod_zip will then honor the "If-Range" header from clients.

@evanmiller
Copy link
Owner

Yes, adding Last-Modified should allow clients to resume failed downloads.

@mecampbellsoup
Copy link
Author

@evanmiller why/are CRC32 calculations for each entry in the manifest required to support this feature? It's not immediately clear to my why that would be... if there's some documentation floating around (I haven't found a good explanation) that you're aware of I'd appreciate linking it here! Thanks 🙏

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

2 participants