Inf-IT DAV Clients

davclients@lists.inf-it.com

313 discussions

can't load calendar (MDaemon and cors)
by Marc Cano 06 Sep '18

06 Sep '18

Hello, I'm currently having some trouble configuring CalDavZAP and server for a intranet. We have a webDAV server powered by MDaemon. It's compatible? It works fine with Mozilla Thunderbird. I want to load a calendar from server. At the moment I'm developing the client on a local server https and the webDav it's https too. I don't want login screen, so I've set up the globalAccountSettings. As I do not have permissions to manage the server, I have tried installing plugins for CORS but it does not work very well. I always get the same message: *** OPTIONS https://webmail.cag.es/webdav/public-calendars/comercial/h4014 401 (Unauthorized): Failed to load https://webmail.cag.es/webdav/public-calendars/comercial/h4014: Response for preflight does not have HTTP ok status. webdav_protocol.js:675 Error: [DAVresourceDelegation: 'REPORT https://[my_mail]@ webmail.cag.es/webdav/public-calendars/comercial/h4014'] code: '0' status: 'error' (this error code usually means network connection error, or your browser is trying to make a cross domain query, but it is not allowed by the destination server or the browser itself) *** Is that all that can be done by the client? Some error in config.js? (the only thing I see is a white screen) Here is my config.js: // config.js var globalAccountSettings=[ { href: 'https://webmail.cag.es/webdav/public-calendars/comercial/h4014', userAuth: { userName: 'xxxxxxxxxxx', userPassword: 'xxxxxxx' }, // crossDomain: true, // withCredentials: false, timeOut: 90000, lockTimeOut: 10000, checkContentType: false, settingsAccount: true, delegation: true, hrefLabel: null, forceReadOnly: null, ignoreAlarms: true, backgroundCalendars: [] }, ]; var globalBackgroundSync=true; var globalSyncResourcesInterval=120000; var globalEnableRefresh=false; var globalEnableKbNavigation=true; var globalInterfaceLanguage='es_ES'; var globalInterfaceCustomLanguages=[]; var globalSortAlphabet=' 0123456789'+ 'AÀÁÂÄÆÃÅĀBCÇĆČDĎEÈÉÊËĒĖĘĚFGĞHIÌÍÎİÏĪĮJKLŁĹĽMNŃÑŇOÒÓÔÖŐŒØÕŌ'+ 'PQRŔŘSŚŠȘșŞşẞTŤȚțŢţUÙÚÛÜŰŮŪVWXYÝŸZŹŻŽ'+ 'aàáâäæãåābcçćčdďeèéêëēėęěfgğhiìíîïīįıjklłĺľmnńñňoòóôöőœøõō'+ 'pqrŕřsśšßtťuùúûüűůūvwxyýÿzźżžАБВГҐДЕЄЖЗИІЇЙКЛМНОПРСТУФХЦЧШЩЮЯ'+ 'Ьабвгґдеєжзиіїйклмнопрстуфхцчшщюяь'; var globalSearchTransformAlphabet={ '[ÀàÁáÂâÄäÆæÃãÅåĀā]': 'a', '[ÇçĆćČč]': 'c', '[Ďď]': 'd', '[ÈèÉéÊêËëĒēĖėĘęĚě]': 'e', '[Ğğ]': 'g', '[ÌìÍíÎîİıÏïĪīĮį]': 'i', '[ŁłĹĺĽľ]': 'l', '[ŃńÑñŇň]': 'n', '[ÒòÓóÔôÖöŐőŒœØøÕõŌō]': 'o', '[ŔŕŘř]': 'r', '[ŚśŠšȘșŞşẞß]': 's', '[ŤťȚțŢţ]': 't', '[ÙùÚúÛûÜüŰűŮůŪū]': 'u', '[ÝýŸÿ]': 'y', '[ŹźŻżŽž]': 'z' }; var globalResourceAlphabetSorting=true; var globalNewVersionNotifyUsers=[]; var globalDatepickerFirstDayOfWeek=1; var globalHideInfoMessageAfter=1800; var globalEditorFadeAnimation=666; var globalEventStartPastLimit=3; var globalEventStartFutureLimit=3; var globalTodoPastLimit=1; var globalLoadedCalendarCollections=[]; var globalLoadedTodoCollections=[]; var globalActiveCalendarCollections=[]; var globalActiveTodoCollections=[]; var globalCalendarSelected=' https://webmail.cag.es/webdav/public-calendars/comercial/h4014'; var globalActiveView='multiWeek'; var globalOpenFormMode='double'; var globalTodoListFilterSelected=['filterAction', 'filterProgress']; var globalCalendarStartOfBusiness=8; var globalCalendarEndOfBusiness=17; var globalDefaultEventDuration=120; var globalDisplayHiddenEvents=false; var globalTimeZoneSupport=true; var globalTimeZone='Europe/Berlin'; var globalTimeZonesEnabled=['Europe/Berlin']; var globalRewriteTimezoneComponent=true; var globalRemoveUnknownTimezone=false; var globalShowHiddenAlarms=false; var globalIgnoreCompletedOrCancelledAlarms=true; var globalMozillaSupport=true; var globalWeekendDays=[0, 6]; var globalAppleRemindersMode=true; var globalSubscribedCalendars={ hrefLabel: 'Subscribed', calendars: [ { href: 'https://webmail.cag.es/webdav/public-calendars/comercial/h4014', userAuth: { userName: 'xxxxxxxxxxxx', userPassword: 'xxxxxxxxxx' }, typeList: ['vevent', 'vtodo'], ignoreAlarm: true, displayName: 'Remote Calendar 1', color: '#ff0000' }, ] }; -- <http://www.bonarea.com> -- CONFIDENCIALITAT. Aquesta comunicació i els seus annexes contenen informació confidencial i/o secreta, sotmesa a secret professional i que té com a destinatari única i exclusivament a la persona a la que va dirigida. Si vostè no és el destinatari, l’informem que no està autoritzat a llegir-la, copiar-la o divulgar-la, de manera que li preguem que ho notifiqui immediatament a CORPORACIÓ ALIMENTARIA GUISSONA S.A. i desprès elimini aquest correu i qualsevol còpia del mateix. Queda, per tant, prohibida la lectura, divulgació o distribució d’aquest correu electrònic i dels seus annexes, a qualsevol persona que no sigui el seu destinatari, sense el consentiment escrit de CORPORACIÓ ALIMENTARIA GUISSONA S.A. PROTECCIÓ DE DADES. De conformitat amb el disposat en la normativa vigent en matèria de protecció de dades, li comuniquem que les dades de caràcter personal utilitzades en aquest enviament es troben incloses en fitxers la titularitat dels quals correspon a CORPORACIÓ ALIMENTARIA GUISSONA S.A. Tanmateix, l’informem que les dades contingudes en aquest enviament seran incorporades en fitxers de CORPORACIÓ ALIMENTARIA GUISSONA S.A. amb l’única finalitat de mantenir i administrar la relació establerta, de manera que seran conservades mentre existeixi un interès mutu i no seran comunicades a tercers excepte obligació legal. Per exercir els drets d’accés, rectificació, cancel·lació, oposició, limitació del tractament i portabilitat de les dades, s’haurà de dirigir per escrit, acreditant la seva identitat, a CORPORACIÓ ALIMENTARIA GUISSONA S.A. C/ Traspalau, 8, 25210 Guissona (Lleida) o fer-ho a través de la direcció de correu electrònic lopd(a)bonarea.com <mailto:lopd@bonarea.com>. Si considera que les seves dades no estan sent tractades segons estableix la llei podrà presentar una reclamació davant l’autoritat de control (http://www.agpd.es <http://www.agpd.es>) Per més informació pot consultar la nostra Política de Privacitat (http://www.bonarea-agrupa.com/PrivacyPolicy <http://www.bonarea-agrupa.com/PrivacyPolicy>). CONFIDENCIALIDAD. Esta comunicación y sus anexos contienen información confidencial y/o secreta, sometida a secreto profesional y que tiene como destinatario único y exclusivo la persona a la que va dirigida. Si usted no es el destinatario, le informamos que no está autorizado a leerla, copiarla o divulgarla, por lo que le rogamos que lo notifique inmediatamente a CORPORACIÓN ALIMENTARIA GUISSONA S.A. y tras ello elimine este correo y cualquier copia del mismo. Queda, por tanto, prohibida la lectura, divulgación o distribución de este correo electrónico y de sus anexos, a cualquier persona que no sea su destinatario, sin el consentimiento escrito de CORPORACIÓN ALIMENTARIA GUISSONA S.A. PROTECCIÓN DE DATOS. De conformidad con lo dispuesto en la normativa vigente en materia de protección de datos, le comunicamos que los datos de carácter personal utilizados en este envío se encuentran incluidos en ficheros cuya titularidad ostenta CORPORACIÓN ALIMENTARIA GUISSONA S.A. Asimismo, le informamos que los datos contenidos en este correo y los que lo sucedan, así como sus anexos o fax, serán incorporados a los ficheros de CORPORACIÓN ALIMENTARIA GUISSONA S.A. con la única finalidad de mantener y administrar la relación establecida, de forma que serán conservados mientras exista un interés mutuo para ello y no serán comunicados a terceros salvo obligación legal. Para ejercitar los derechos de acceso, rectificación, cancelación, oposición, limitación del tratamiento y portabilidad de los datos, deberá dirigirse por escrito, acreditando su identidad, a CORPORACIÓN ALIMENTARIA GUISSONA S.A. C/ Traspalau 8, 25210 Guissona (Lleida) o hacerlo a través de la dirección de correo electrónico lopd(a)bonarea.com <mailto:lopd@bonarea.com>. Si considera que sus datos no están siendo tratados según establece la ley podrá presentar una reclamación ante la autoridad de control (http://www.agpd.es <http://www.agpd.es>). Para más información puede consultar nuestra Política de Privacidad (http://www.bonarea-agrupa.com/PrivacyPolicy <http://www.bonarea-agrupa.com/PrivacyPolicy>). CONFIDENTIALITY. This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication, along with any documents, files or attachments, may not be reproduced or distributed without the express written consent of CORPORACIÓN ALIMENTARIA DE GUISSONA, S.A. DATA PROTECTION. In compliance with the Personal Data Protection Law and GDPR we inform you that your personal information is included in a personal information filing system owned by CORPORACIÓN ALIMENTARIA DE GUISSONA, S.A. We also inform you that your personal information included in this email, along with any documents, files or attachments, will be included in a personal information filing system owned by CORPORACIÓN ALIMENTARIA DE GUISSONA S.A. You may exercise your rights of access, rectification, cancellation, objection, portability and restriction of processing of your personal data, at any time, by sending a written notice, attaching a photocopy of a document evidencing your identity, to CORPORACIÓN ALIMENTARIA GUISSONA S.A. C/ Traspalau 8, 25210 Guissona (Lleida), or to lopd(a)bonarea.com <mailto:lopd@bonarea.com>. If you consider that we are not processing your personal data as required by law, you can exercise your right to lodge a complaint with a supervisory authority (http://www.agpd.es <http://www.agpd.es>). For more information, you may visit our Privacy Policy (http://www.bonarea-agrupa.com/PrivacyPolicy <http://www.bonarea-agrupa.com/PrivacyPolicy>).

2 1

Issues with globalNetworkCheckSettings and multiple items in additionalResources
by Linus Lüssing 06 Aug '18

06 Aug '18

Hi, I'm currently having some trouble configuring CalDavZAP with multiple additionalResources. Whenever I try to add more than one item to additionalResources, only the last one seems to get listed in the web-ui. I'm probably just having some simple configuration mistake but due to the awkward behaviour I was wondering whether this could be a bug within CalDavZAP, too. In the end I would like to have CalDavZAP list a set of shared resources, together with the user specific ones after a user logs in. /etc/radicale/rights currently looks like this: ----- [general] user: .+ collection: ^shared(/.+)?$ permission: rw [private] user: .+ collection: ^%(login)s(/.+)?$ permission: rw ----- If I use the following in CalDavZAP's config.js, I can reproduce the issue of only having 'another-cal.isc' shown in the web-ui: ----- var globalNetworkCheckSettings={ href: 'http://foo.example.com/shared/', additionalResources: ['some-cal.ics', 'another-cal.ics'], hrefLabel: null, forceReadOnly: null, settingsAccount: true, checkContentType: true, timeOut: 9000, lockTimeOut: 10000, } ----- The rest of config.js is left untouched. Any thoughts? Regards, Linus

2 1

Duplicate UID after copy
by Johan Vromans 24 Jul '18

24 Jul '18

Hi, When I copy (clone) an appointment (click on it, and [Copy] && [Save]) I en dup with two appointments that have the same UID. Even if this is permitted by the specs, there are some tools that have problems with this -- they require all events to have unique ids. Is it possible to generate a new UID for the new appointment? Also: The latest InfCloud release was in 2015. Is it still under active development/maintenance? Regards, Johan

2 2

Who's updating
by Johan Vromans 17 Jul '18

17 Jul '18

When I have a repeating appointment, and delete one of the occurrences, a lot of changes need to be made to the event -- e.g. EXDATE, OCCURRENCE, ... Just wondering... Does the client have to do all this, or is it just an API call to the caldav server?

2 2

InfCloud settings
by Benjamin Aucher 11 Jun '18

11 Jun '18

Hello, I would like to setup InfCloud to use with my cpanel calendar and contacts. I can access to my calendar with CalDav in Ligthning but I am not able to configure it in InfCloud. Cpanel give theses url : https://mydomain.fr:2080/rpc/principals/davtest@mydomain.fr https://mydomain.fr:2080/rpc/calendars/davtest@mydomain.fr/calendar:c9a60fa… https://mydomain.fr:2080/rpc/addressbooks/davtest@mydomain.fr/contacts~4dc3… In the config.js file, I only have change this : var globalNetworkCheckSettings={ href: 'https://mydomain.fr:2080/rpc/principals/', timeOut: 90000, lockTimeOut: 10000, checkContentType: true, settingsAccount: true, delegation: true, additionalResources: [], hrefLabel: null, forceReadOnly: null, ignoreAlarms: false, backgroundCalendars: [] }; But the login seems fail... Have you any suggestion ? Thank you Benjamin

1 0

Border
by Pierre Couderc 26 May '18

26 May '18

Thanks again for this fine caldavzap ! Is it possible to edit some fullcalendar.css (or other...) to get a light vertical border between day cells in the month view and/or horizontally center the day number in the day cell ? I have tried to go inside the css but did not success... And too are there alternate css...? Anyway the current one is very fine. PC

2 2

caldavzap gives me a white page
by Jean-Luc Mounier 16 Apr '18

16 Apr '18

Hi, I have created a php script which produces .ics files from Volley match teams. These calendars are read only calendars and access is free (no login/password). I can subscribe theses calendars in many different applications but CalDavZAP 0.13.1 gives me a white page. I have manually add OPTIONS and PROPFIND http answers but I'n not really sure that it is correct. I think I don't understand the meaning these elements and what are the minimum answer. FireFox tells me that there is an XML error but I don't know where ? Here a part of the config.js file var globalAccountSettings=[ {href: 'https://calendrier.charentonvolley.fr:443/smn1', hrefLabel: 'N1', forceReadOnly: true, settingsAccount: false, checkContentType: true, userAuth: {userName: '', userPassword: ''}, timeOut: 90000, lockTimeOut: 10000, delegation: false, ignoreAlarms: true, backgroundCalendars: []}, ]; Jean-Luc

2 3

CORS
by Joachim Schiele 28 Mar '18

28 Mar '18

hey, i wanted to create a wordpress plugin using caldavzap but while i was able to use: https://demo13.nextcloud.bayton.org/apps/calendar/ from thunderbird, it seems to fail from caldavzap: var globalNetworkCheckSettings={ href: "https://admin:admin@demo13.nextcloud.bayton.org/remote.php/dav/calendars/ad…", userAuth: { userName: 'admin', userPassword: 'admin' }, timeOut: 90000, lockTimeOut: 10000, checkContentType: true, settingsAccount: true, delegation: true, additionalResources: [], hrefLabel: null, forceReadOnly: null, ignoreAlarms: false, backgroundCalendars: [] } the error it reports is: OPTIONS https://demo13.nextcloud.bayton.org/remote.php/dav/calendars/admin/personal/ 401 (Unauthorized) 16:59:17.819 jquery-2.1.4.min.js:4 OPTIONS https://demo13.nextcloud.bayton.org/remote.php/dav/calendars/admin/personal/ 401 (Unauthorized) Failed to load https://demo13.nextcloud.bayton.org/remote.php/dav/calendars/admin/personal/: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access. The response had HTTP status code 401. Error: [netCheckAndCreateConfiguration: 'PROPFIND https://admin:admin@demo13.nextcloud.bayton.org/remote.php/dav/calendars/ad…'] code: '0' status: 'error' - see https://www.inf-it.com/caldavzap/readme.txt (cross-domain setup) we had also tried the calendar from config.js: href: location.protocol+'//'+location.hostname+ (location.port ? ':'+location.port: '')+ location.pathname.replace(RegExp('/+[^/]+/*(index\.html)?$'),'')+ '/caldav.php/', but this also failed. the overall question now would be: can one use these two callendards without doing server side modifications to it? if a server side modification would be required to use caldavzap then one would not be able to use caldavzap with an arbitrary online resource and ATM i think that this is the case. can someone please tell me that i'm wrong plz? regards, joachim schiele -- Joachim Schiele nixcloud GmbH 004915204145347 blog: http://lastlog.de/blog wiki: http://lastlog.de/wiki GPG: C11CFB9FFA7A5F4EEDCC59BCAC10E1AC6D8F75EE (here: https://lastlog.de/blog/about.html)

2 2

Using HTTP Basic Auth
by l-infit＠wieh.eu 16 Mar '18

16 Mar '18

Hi! I just want to share my hack, as it will likely be valuable to others as well. I have a not so uncommon setup: People login via HTTP Basic Authentication (popup window in the webbrowser). The webserver manages the login via LDAP. Once logged in, they have access to several webservices like wiki, file safe (Nextcloud or something), InfCloud and others. So clearly I do not want any login page. The login credentials are known by the webserver and webbrowser. The webbrowser will happily send them again without user interaction. Officially there seems to be no way to login without the login screen, but without hard-coding credentials in the config.js. Ok. Generally, this is not so easy, because in Javascript you cannot access the browser’s authentication cache—for good reason. But in my case (and maybe in your case, too) the InfCloud files are provided by the same webserver that also serves as the WebDAV server (DAViCal in my case); and also by the same vhost. (This might later be important—see below. I have no special subdomain for DAViCal.) So there are no (additional) security concerns in sending the credentials once again from the browser to the webserver and back again, so I can read them in my Javascript. Here is what I have done: 1) Rename InfCloud’s index.html to index.php. You should try this out. Maybe you better use another language, if PHP is not available to your webserver. In my case, DAViCal is running on the same webserver, which is written in PHP. So, obviously, I can run PHP scripts. 2) In the lines around 620 in index.php, there are some hidden form fields (<input id="foo" type="hidden" value=""/>. Add two more like this: <input id="foo-login" type="hidden" value="<?=htmlspecialchars($_SERVER['PHP_AUTH_USER'])?>"/> <input id="foo-pw" type="hidden" value="<?=htmlspecialchars($_SERVER['PHP_AUTH_PW'])?>"/> The effect is, that the user gets back an HTML file with their login credentials in cleartext in there. Don’t do this, if this is risky in your setup. In most cases this should not be risky, as the browser knows the credentials anyway; as well as anyone who can read the traffic between the browser and the InfCloud webserver. 3) In the beginning of the index.php, inside the <head></head> section, there are several lines starting with “<script”. Move all these lines to the end of the document, right before the closing </body> tag. The Javascript needs to be loaded after the rest of the document, because otherwise the Javascript code in the beginning would not have access to the content of the document, i.e. to our credentials. 4) In config.js, enable the globalAccountSettings method (that one with the hard-coded credentials). But instead of really hard-coding some credentials there, you type (for example, if you have DAViCal installed in /cal/ and rewrite the URLs in your webserver config, so you can omit the part “/caldav.php”): href: 'https://example.com:443/cal/'+document.getElementById('foo-login').value+'/', userAuth: { userName: document.getElementById('foo-login').value, userPassword: document.getElementById('foo-pw').value }, If both the WebDAV server and the InfCloud files are below the same principal URL (same vhost), then a better solution would be, if InfCloud would simply try to access the WebDAV server without sending any login credentials. The WebDAV server would then reply with 401 and the browser would resend the request with the already-known credentials in the request header. This would be much less of a hack. Maybe somene else wants to try that. Love Torsten

1 0

InfCloud is failing on me...
by Johan Vromans 09 Mar '18

09 Mar '18

All of a sudden InfCloud is missing events. I'm running InfCloud 0.13.2.rc2 since the end of 2015 using FireFox on Fedora. The DAViCal server is running on a separate system. InfCloud didn't change and neither did the DAViCal server. I did upgrade FireFox as part of regular system upgrades. This morning I noticed, the hard way, that a repeating event was missing from InfCloud. It is just gone. All occurrences, including past occurrences. The event is on the server, since other clients (Android phones and tablets) display it. This worries me very much. Is there anything I can do to find out what is going on? I tried cahce_update but that didn't make a difference. Update: InfCloud with Chromium doesn't show the missing events either.

2 5

← Newer
1
2
3
4
5
6
7
8
...
32
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Inf-IT DAV Clients