Status: Fixed
I have now added a module called http-options which can be used to
configure http options, notably the 100-Expect.
I am unsure if it will break existing installations if I disable
it by default, so it is still enabled but can be disabled by the
switch --disable-expect100-continue.
You can set this option in the GUI under "Advanced options".
git-svn-id: https://duplicati.googlecode.com/svn/trunk@713 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
The outer-hash fix was done with r711.
In r711 there is also an option to run Duplicati.CommandLine with the "verify" command.
Finally r711 also has an option to create a verification file on the backend,
using the --create-verification-file option.
This commit adds a small python script that can be used to verify the files
on the remote backend without using the backup password.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@712 59da171f-624f-0410-aa54-27559c288bec
This commit includes an option to create an unencrypted verification file.
There is now a check to see if all volumes mentioned in the manifest exists,
before performing backup/restore operations.
This check is also performed on cleanup.
There is now a check that prevents auto-cleanup from removing more than
2 orphan files.
If a delete-older-than or delete-all-but-n-full is interrupted, the leftover
files will not be auto-deleted but must be deleted with the cleanup command,
which allows the user to see what files are delete.
Update issue #360
Status: Fixed
There is now a complete verification chain, where the manifest hashes are verified backwards.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@711 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
Changed so the default storage path for signature cache is in the non-roaming folder, if the client is windows based.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@686 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
I found and fixed the issue, I was using an int instead of a long for the filesize,
which caused it to truncate.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@683 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
That is an incorrect warning, the priority is applied despite the warning.
I have fixed the code so the warning does not appear anymore.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@675 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
I have now removed the code required to activate the deprecated AES crypt encryption, but kept the code required to decode it,
git-svn-id: https://duplicati.googlecode.com/svn/trunk@670 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
It was supposed to write an error message like:
When listing the folder <foldername> the file <filename> was listed, but the server now reports that the file is not found.
This can be because the file is deleted or unavailable, but it can also be because the file extension .aes is blocked by the web server. IIS blocks unknown extensions by default.
Error message: 404 - File not found
Unfortunately the error message was incorrectly formated so you got a highly misleading message instead.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@658 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
It turns out that it was an invalid error message.
Actually it should request that the user enter a destination folder.
I also changed the summary page to not show the inserted temporary folders.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@657 59da171f-624f-0410-aa54-27559c288bec
Changed the non-streaming file-backend interface to use sytem copy calls rather than
manual stream copy.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@654 59da171f-624f-0410-aa54-27559c288bec
