Re: [Burp-users] Resume big file transfert when network lost

[Graham K. <gr...@gr...>]

On Mon, November 14, 2016 10:32 pm, Marcin Mirosław wrote:
> W dniu 14.11.2016 o 11:41, Graham Keeling pisze:
>
> Hi!
>
>
>> On Sun, Nov 13, 2016 at 10:23:28PM +0100, ph...@ma... wrote:
>>> Hello people,
>>>
>>> I'm a new user of Burp and I'm testing is capability to minimise the
>>> network usage.
>>>
>>> Is there a way to have a "resume file" capability ?
>>> If i kill the client during a big file transfer, it will restart from
>>> the beginning of this file even with the working_dir_recovery_method =
>>> resume
>>> I try protocol 1 and protocol 2 with the same issue… Is it normal ?
>>> Did
>>> I miss something ?
>>>
>>> Thanks for help.
>>>
>>> Phil
>>
>> Hello,
>>
>> There is no "resume file" capability.
>>
>> Protocol 1 works at file level granularity.
>>
>> Protocol 2 works at a combination of file level and block level
>> granularity,
>> which in practice should mean that you should be able to resume within
>> the
>> last 25MB that has been transferred. If it doesn't, there is a bug.
>
>
> What will happen when bugs (github) #503 and #494 will be fixed? Will
> resume work in protocol2?

There are fixes for 494 in 2.0.52, but since it is a bug that only gets
exposed after a long period of usage, I have left the issue open until
a fair amount of time has passed.

Issue 503 is related to deleting unused data, not resuming, so is only
tangentially relevant.

Resume should currently work in protocol 2. If it doesn't there is a bug.
There are automatic tests that interrupt backups and resume them for both
protocol 1 and 2, but they only check whether the resultant backups are
OK. They don't check whether some data was transferred twice.