Full support for DAViCal in older version. Atmail CalDAV client - a jQuery CalDAV client, support for delegation and shared calendars.DAViCal Web Client - simple graphical interface.Webical - no active development anymore.CalDavZAP - Open source web CalDAV client / HTML5 Javascript+jQuery web application (compatible with Safari, Webkit, Chrome and Firefox).AgenDAV - Free software, featuring Fullcalendar.ZideOne A MAPI message store provider which converts Outlook into a real CalDAV/GroupDAV client (nonfree) (deprecated, no longer available).OpenChange/SoGo seems to have worked out a built-in solution for their project that may be usable?.OpenConnector for Outlook 2003+, post 2007-Dec releases.iCal4OL A perfect 2-Way Synchronization with Google Calendar, DAViCAL and WebCalendar! (nonfree).cFos Outlook DAV Cloud synchronisation of your Outlook calendar, tasks, and contacts (nonfree).Atmail Sync for Outlook A Microsoft Outlook 2007 & 2010 Add-in to open-standard CalDAV (calendaring) and CardDAV (contacts) protocols to sync to the Atmail server (nonfree).Outlook Several extensions for Outlook are available:.SOHO Organizer will work with basic functions from DAViCal 0.9.2 onwards, more complete support arrived in 0.9.3.iCal version 3.0.1 onward from OS 10.5, and since DAViCal release 0.9.2 onwards.Kontact / Akonadi / KOrganizer (via WebDAV as at Sept 2009).Postbox Postbox and its Postbox Lightning add-on, working very well.Mozilla Thunderbird (more precisely, Mozilla Lightning & Mozilla Sunbird).Template:TOCrightSo far the available CalDAV clients which have been verified to work with DAViCal in at least some manner are: There is a registry key named FileSizeLimitInBytes under HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> WebClient -> Parameters.In Wikipedia: Comparison of CalDAV and CardDAV implementations To make this size large, change the registry entry on the client machine. This is because Windows Explorer has a limit of the file size downloaded from webdav server. This happens when you map webdav as a network drive, and tries to copy a file larger than about 50MB from the network drive to a local folder. Windows Explorer reports "file size exceeds the limit allowed and cannot be saved" ¶ Restart your seafile server and try again. If you deploy SeafDAV behind Nginx/Apache, make sure to change the value of share_name as the sample configuration above. If not, modify it and restart seafile server. Check whether you have enabled = true in nf. Frequently Asked Questions ¶ Clients can't connect to seafdav server ¶īy default, seafdav is disabled. So it is recommended to use a webdav client software such as Cyberduck. Or you can use davfs2 from the command line.įinder's support for WebDAV is also not very stable and slow. You can use file manager such as Nautilus to connect to webdav server. If you use a self-signed certificate, you have to add the certificate's CA into Windows' system CA store. It's generally recommended to use Windows Explorer to map a webdav server as network dirve. But it requires a valid certificate on the server. For Vista and later versions: Windows Explorer supports HTTPS connection.So for security, the only viable option is to use third-party clients, such as Cyberduck or Bitkinex. For Windows XP: Only non-encryped HTTP connection is supported by the Windows Explorer.The client recommendation for WebDAV depends on your Windows version: If you want better performance, please use the sync client instead. So WebDAV is more suitable for infrequent file access. That's because the local file system driver sends a lot of unnecessary requests to get the files' attributes. The access to the webdav server may be slow sometimes.That's because each file needs to be committed separately. Uploading large number of files at once is usually much slower than the syncing client.Please first note that, there are some known performance limitation when you map a Seafile webdav server as a local file system (or network drive). So if you want to support file upload larger for 4GB, we suggest you install Nginx version >= 1.8.0 and add proxy_request_buffering off to Nginx configuration. It may stop proxying the body in the middle. But it seems when file size is very large, the buffering mechanism dosen't work well. After the body is completely received, Nginx will send the body to the upstream server (seafdav in our case). Location / seafdav īy default Nginx will buffer large request body in temp file. Windows Explorer reports "file size exceeds the limit allowed and cannot be saved" SeafDAV Configuration for 7.0 or older versions
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |