You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2017. It is now read-only.
For serves that provide a Content-Length HTTP header, we could possibly do this. The caveat of course is that the spec does not require servers to provide this header and so we won't always know a file size until we grab the file.
If somebody wants to implement this, I'd like to see it this way:
If no option is specified, then don't restrict file size.
This is probably a security issue, to be honest, because a malicious attacker could serve a fake stream to fill up the file system where Maltrieve stores the data. But in that case they probably won't use the Content-Length header and so this wouldn't fix that. So, separately from any code implementation as described above, the documentation should make clear that dumpdir needs to be on a non-system partition to avoid a denial of service.
I appreciate this question, it's really helpful!
krmaxwell
changed the title
Question or Feature Request
Feature Request: download size filter
Apr 4, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Does it have some sort of download size filter? So we can avoid downloading a 1GB file?
The text was updated successfully, but these errors were encountered: