DAVbox 1.4.2 release notes
Requirements
You need Java Web Start running on Java 1.8 or higher.
Installation
Just click on
https://www.pincette.net/davbox/launch.jnlp.
If DAVbox doesn't seem to synchronize subfolders this probably means the server
doesn't report its lack of support for the value infinity
for the
Depth
header. In that case you can use the link
https://www.pincette.net/davbox/launchr.jnlp.
Changes
Changes Since Version 1.4.1
Bug fixes:
- Allow passwords with accents.
Changes Since Version 1.4
Bug fixes:
- Conflict resolution failed when the remote URL didn't have a trailing slash.
- The inclusions menu item stayed enabled during synchronisation.
- On Windows files were locked for a few seconds after an upload.
Changes Since Version 1.3.9
New features:
- It is now possible to set inclusions, which are the opposite of exclusions. This means you can specify which patterns should be considered for synchronisation. The rest will be ignored.
Changes Since Version 1.3.8
Bug fixes:
- False conflicts at initial unidirectional synchronisation.
- False conflicts with DeltaV server.
Minor changes:
- Add
Translate: F
header for IIS compatibility. - Increase the remote update time margin from 2 to 5 seconds. This margin copes with the fact that the Last-Modified header may be newer than the Date header in the last PUT response of a file.
- Update the favorites in macOS Finder and Windows Explorer only when they have changed.
Changes Since Version 1.3.7
Bug fixes:
- When there are conflicts the local monitor thread should be paused.
- Automatic conflict resolution by upload when the "rename" option is turned on is removed, because it is confusing and causes uploads for down synchronisations.
- After an upload the file lock is not released immediately on Windows.
Minor changes:
- Change the User-Agent header to DAVbox.
- Write more information to the log when starting up and during synchronizations.
Changes Since Version 1.3.6
Bug fixes:
- When doing unidirectional synchronization files on the target side that don't come from the source side should be ignored.
- When an invalid license file is given by the user there is no error message. Instead the file dialog reopens, which is not clear for the user.
- Tray icon is invisible on Mac OS X in dark mode.
Changes Since Version 1.3.5
Bug fixes:
- When the
${select}
configuration feature is used the directory "${select}" is always created. It is not used however. - Favourites are only created when the synchronizations are edited, not at the first start.
- Don't open the initial edit synchronizations dialog box when either the "-config-readonly" or the "-synchronizations-only" option is used.
Minor changes:
- Warn that a local folder is required when using the
${select}
configuration feature and exit when the user confirms no local folder will be selected. - Wait for an Internet connection to become available while starting.
- New mechanism to brand any label in the application.
- Avoid command window popping up while starting on Windows.
Changes Since Version 1.3.4
Bug fixes:
- Loading the saved URL credentials may skip some. This only occurs when you have several synchronization couples.
- On Windows it is not possible to select a folder. It only accepts files.
Minor changes:
- Add local folders to the Finder sidebar on Mac OS X.
Changes Since Version 1.3.3
Bug fixes:
- When multiple synchronization couples match a plugin only one is checked for modifications.
- Uninstalling DAVbox should count down the license usage.
- Sometimes there is a database exception at the very first run, but without impact on the database.
- Repertiores -> repertoires in the French translation.
- Allow to have no synchronization couples at all.
- Removing a remote folder, then synchronizing and then reinserting the same remote folder causes conflicts on everything in the folder.
- Exception when downloading a file of more than 2GB with Content-Length header.
- Regular expressions in the exclusions list that have backward slashes have them converted to forward slashes.
- Relative directories in the synchronization settings, when entered interactively, resolve against the working directory instead of the user's home directory.
Minor changes:
- Added distinctions between errors and conflicts on one side and normal notifications on the other.
- Added username/password fields to synchronization couples.
- Branded the license registration error messages.
- Created white tray-icon for Windows 10.
- Improved collection of diagnostics.
- Simplified uninstallation.
- Extended exclusion syntax for better selectivity.
- Added inversion operator to the exclusion syntax.
- Introduced
${select}
in configuration. This can be used for remote configurations where the user is asked to choose the local folder. - Use the native file choosers.
Changes Since Version 1.3.2
Bug fixes:
- It is not possible to get rid of certain conflicts when the files have been deleted manually in the meantime. This blocks further synchronization.
- Class loader issue when loading plugins.
Minor changes:
- The new command-line option "-remote-plugin", which allows the deployment of a plugin centrally on the server.
- Reintroduce a timeout on the server connections, because sometimes they can get stuck after the computer has slept.
Changes Since Version 1.3.1
Bug fixes:
- On Windows the local deletion of a folder may fail because it is locked by the monitoring feature.
- When the local deletion of a file fails it is still marked as deleted, causing a re-upload at the next synchronization cycle.
Changes Since Version 1.3
Bug fixes:
- When a server doesn't support "Depth infinity" but reports it correctly, the folder tree is constructed incorrectly.
- Exception because of a race condition while creating the database at the very first run. This has no impact on the database.
- Don't try to upload a modified configuration to the remote configuration.
Changes Since Version 1.2.9
New features:
- Monitor local folders for immediate update on the server.
- New branding mechanism for white label usage.
- Synchronization direction can be configured per synchronization pair.
- New menu-item to open the local folders.
- Add local folders to Windows Explorer favorites.
- New plugin facility to check for changes on the server in another way than through the standard collection tree fetching. This can make DAVbox react more quickly to changes on the server.
- Mac OS X notifications.
- New command-line options "-uninstall" and "-plugin-interval".
Bug fixes:
- Connect to Growl even when it was started after DAVbox.
Minor changes:
- Put derby.log file in the settings folder.
- Use the standard folder for the settings on Windows and Mac OS X.
Changes Since Version 1.2.8
Bug fixes:
- The home folder is not processed correctly for Pincette servers.
- When wrong credentials are given while adding a synchronization couple an error message is shown instead of asking them again.
Minor changes:
- New
-truststore
command-line option, which can be used in centrally deployed JNLP-files. When your server doesn't have a valid SSL-certificate you can put that certificate in a Java truststore on the server itself. This option should get the URL to the truststore. It will be fetched using the HTTP-protocol. - Improved tray icon for Java 8.
- Improved German translations. (Thanks to Matthias Kasperidus.)
Changes Since Version 1.2.7
Minor changes:
- Add the
Permissions
attribute to the JAR-file, which is now mandatory in Java 7.
Changes Since Version 1.2.6
Minor changes:
- Introduce the ${home} parameter in URLs, which works only with the Pincette WebDAV-server. A URL of the form https://hostname/${home}/ will be replaced with the user's home folder on Pincette.
- Improve the German translation.
Changes Since Version 1.2.5
Bug fixes:
- On Windows the uninstall procedure can't remove everything.
Changes Since Version 1.2.4
Bug fixes:
- Exception when the server doesn't return etags.
Changes Since Version 1.2.3
Bug fixes:
- The validity of a host-bound license shouldn't depend on the presence of a configuration on the server.
- When there is no database yet adding a synchronization couple fails.
Minor changes:
- On the local computer deleted files are moved to the folder "DAVboxTrash" in the home folder instead of to hidden folders, which makes it easier to recover them.
Changes Since Version 1.2.2
Bug fixes:
- Database reinitialization error.
Changes Since Version 1.2.1
Bug fixes:
- An interrupted download or upload can delete the file during the next synchronization cycle.
Minor changes:
- When resolving conflicts it is now possible to choose the same resolution for all conflicts with one click.
- Only one instance of DAVbox can run at the same time.
Changes Since Version 1.2
Bug fixes:
- Database corruption is possible when the disk of the local computer is full.
- Retry the download of the JAR-file when it fails in the local file encoding workaround for Mac OS X.
Minor changes:
- Some more technical menu-items have been moved to a submenu.
- Show full and wrapped path names in the conflicts dialog box instead of truncated path names with a tooltip.
- Automatically add a trailing slash to an URL if it is missing when setting the synchronizations.
Changes Since Version 1.1.10
New features:
- When the path of the local folder is not absolute it will be considered as relative to the user's home folder. This helps when centralizing the configuration on a server.
- It is now possible to create an unlimited license that is bound to one server, which makes centralized deployments easier.
- Menu-item for for showing the most recent updates, which can be opened with a click.
- Menu-item for clearing the log.
- Menu-item for uninstalling the application.
Bug fixes:
- The response of a PUT call isn't consumed, which disturbs the rest of the dialogue.
- Exception when trying to produce the error message of an unknown HTTP-code.
- Pending synchronization errors should be removed when their corresponding synchronization couple is removed.
- Sometimes a click won't put a cell in an editable table, such as the synchronizations table, in edit-mode.
Minor changes:
- The application starts without a license but won't synchronize.
- When there are no synchronizations yet DAVbox will open the synchronizations dialog box while starting.
Changes Since Version 1.1.9
Bug fixes:
- There were still filename encoding issues on Mac OS X.
- The license file dialog box doesn't allow to choose a license file with Java 6 on Mac OS X.
- Broken license registration link.
Changes Since Version 1.1.8
Bug fixes:
- DAVbox doesn't start at login on Mac OS X with Java 7.
Changes Since Version 1.1.7
Bug fixes:
- Work-around for the filename encoding issue on Mac OS X with Java 7.
Changes Since Version 1.1.6
Bug fixes:
- The Mac OS X is not detected with Java 7, which disables the start-at-login setting.
- Sometimes DAVbox doesn't recur into subfolders.
- Fix the tray icon crispness problem with Java 7 on Mac OS X.
Minor changes:
- Add the
-config-readonly
command-line option, which is useful for centralised deployments where the user is not allowed to change the configuration. - The directories and URLs in the configuration may now contain the
parameter
${username}
. This enables scenarios where there is one centrally deployed configuration.
Changes Since Version 1.1.5
Bug fixes:
- WebDAV-collections containing a plus sign fail to synchronize.
Changes Since Version 1.1.4
Bug fixes:
- Avoid memory shortage when uploading large files with chunked transfer encoding turned off.
- Always use the content type from the server when uploading files and don't just rely on the filename extension, which doesn't always reflect a known MIME type.
Minor changes:
- URI-encode the
+
sign in path segments, because some servers such as Alfresco don't like this perfectly legal character.
Changes Since Version 1.1.3
Bug fixes:
- Certificates that can't be validated can no longer be accepted.
- When the server returns folders without a trailing slash in their URL an error occurs. This causes a failure with box.net.
- The invalid license file message box has the wrong icon.
Minor changes:
- GUI translations for German, Hungarian and Russian. The help files are not yet translated.
Changes Since Version 1.1.2
Bug fixes:
- The default encoding of an HTTP-response is
identity
instead ofdeflate
. - The extensions for the file rename feature are wrong on the local computer.
Minor changes:
- When downloading files the local timestamp is set to that of the file on the server. This allows you to see locally when the file was updated remotely.
Changes Since Version 1.1.1
Bug fixes:
- Exception when the user has no access to a certain file within the synchronized folder.
- URI-encoding problem when using the recursion option.
Minor changes:
- No longer start with a wait before synchronization when the application starts. This was introduced in version 1.0.7 in order to provide the chance to stop long running synchronizations at the start. However, this increases the possibility of synchronization conflicts if the user starts editing certain documents immediately after login. Instead the pause option is now persistent.
Changes Since Version 1.1
Bug fixes:
- A connection pool problem could cause a false conflict.
- A conflict between a file and a directory isn't always handled correctly.
- Deletions during conflict resolution should also make use of the hidden folder feature.
- Folder URLs from the server that are encoded in UTF-8 but without escaping cause a loop when loading them. Note that such URLs are invalid.
Minor changes:
- Cope with URLs that contain characters that should have been URI-encoded. This is for egroupware.
Changes Since Version 1.0.8
New features:
- Integration with the Growl notification system. If Growl isn't present DAVbox will fall back to a simpler notification method.
- It is possible to change the interval between synchronizations.
- Advanced HTTP-options can be changed.
- The synchronizations table now has an option for each row with which synchronizations can be turned off temporarily.
- Files can be renamed keeping multiple versions instead of being overwritten.
Minor changes:
- The icon will become orange instead of red when there are conflicts and red when there are errors. The notifications use the same colors.
Changes Since Version 1.0.7
Bug fixes:
- When a file is changed during a long-running synchronization the change is missed at the next synchronization.
- The menu-item for conflicts should be greyed out when there are no conflicts at the start of the application.
Minor changes:
- Tolerate the absence of the DAV: namespace for the
collection
element inside theresourcetype
element. This is for egroupware. - Show a message when URLs are entered in the synchronizations list that are not WebDAV-collections.
- Confirm quit when a synchronization is running.
- Translation in French.
Changes Since Version 1.0.6
Bug fixes:
- Avoid loops while retrieving the folder tree from the server.
- Local files can be deleted when the connection is lost in the middle of the server folder tree retrieval. These deletions are then propagated to the server at the next synchronization, causing the loss of the files.
- When
View log
is used while the log is already open but hidden behind other windows it should be sent to the front.
Minor changes:
- Start with a wait before synchronizing, which gives the user the chance to modify something before a possibly long running synchronization starts.
- Set a timeout on the connection with the server.
- Accept that some servers return status code 200 instead of 204 for the DELETE method.
- Move files and folders that should be deleted to a hidden folder
.DAVbox
instead of actually deleting them. - Take into account time differences between server and client.
Changes Since Version 1.0.5
Bug fixes:
- The
Start at login
option doesn't work on Mac OS X when the directory~/Library/LaunchAgents
doesn't exist. - Recovery from a broken connection is not always correct.
Minor changes:
- Run DAVbox at the lowest priority.
Changes Since Version 1.0.4
Bug fixes:
- DAVbox blocks the shutdown procedure on Mac OS X.
Minor changes:
- Interpret exclusions as regular expressions instead of patterns when surrounded by brackets ([]).
- Don't show a message box each time there is a connection problem.
Changes Since Version 1.0.3
Bug fixes:
- Exclusions of directories cause the synchronization to go wrong.
Changes Since Version 1.0.2
Bug fixes:
- When a server returns unknown elements besides
collection
in theresourcetype
property, the resource is not recognized as a collection.
Changes Since Version 1.0.1
Minor changes:
- Allow the
status
element to precede theprop
element in a PROPFIND response. Zimbra does this. See also http://bugzilla.zimbra.com/show_bug.cgi?id=74250.
Changes Since Version 1.0
Bug fixes:
- When an error occurred with a file having non-ASCII characters in its name there was no retry at the subsequent synchronization.
Minor changes:
- Accept URLs from server that are encoded in UTF-8, but without URI-encoding applied to them, which is not correct.
Contact Information
Comments and bug reports can be sent to support@pincette.net.