diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2017-07-26 18:35:42 +0200 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2017-07-26 19:07:56 +0200 |
| commit | f2f8e89f08cdf01c83a0b8ab053c65329d85ca90 (patch) | |
| tree | 7ca9caf3e9dfa5caaad5dda836c0d95278a57204 /methods/curl.cc | |
| parent | d7518dba50e2285c41c7002a1d86f876401fd9ea (diff) | |
fail early in http if server answer is too small as well
Failing on too much data is good, but we can do better by checking for
exact filesizes as we know with hashsums how large a file should be, so
if we get a file which has a size we do not expect we can drop it
directly, regardless of if the file is larger or smaller than what we
expect which should catch most cases which would end up as hashsum
errors later now a lot sooner.
Diffstat (limited to 'methods/curl.cc')
| -rw-r--r-- | methods/curl.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/methods/curl.cc b/methods/curl.cc index a19318098..71149217a 100644 --- a/methods/curl.cc +++ b/methods/curl.cc @@ -139,7 +139,7 @@ HttpsMethod::write_data(void *buffer, size_t size, size_t nmemb, void *userp) if (TotalWritten > me->https->Queue->MaximumSize) { me->https->SetFailReason("MaximumSizeExceeded"); - _error->Error(_("File is larger than expected (%llu > %llu). Mirror sync in progress?"), + _error->Error(_("File has unexpected size (%llu != %llu). Mirror sync in progress?"), TotalWritten, me->https->Queue->MaximumSize); return 0; } |