Thanks Ken. I will try and report.
On Wed, Apr 29, 2015 at 12:42 PM, Ken Murchison <murch@xxxxxxxxxxxxxx> wrote:
Support for the expand-property REPORT which CalDAVZAP 0.12.x is using was added to Cyrus in October of last year, which was post-beta10.
If you want to try this with the 2.4 code, you will need to fetch the caldav-2.4 branch from http://git.cyrus.foundation
On 04/29/2015 11:09 AM, Lucas Zinato Carraro wrote:
OK I put caldavzap on cyrus httpd server
In Web browser _javascript_ console:
REPORT http://webserver:8088/dav/principals/user/lucas.carraro/ net::ERR_EMPTY_RESPONSE
---------------------------------------------------------------------------------------
In Cyrus telemetry log: http-18367
---------- lucas.carraro Wed Apr 29 12:00:15 2015
<1430319615<REPORT /dav/principals/user/lucas.carraro/ HTTP/1.1Accept-encoding: gzip, deflate, sdchContent-type: text/xmlAccept-language: pt-BR,pt;q=0.8,en-US;q=0.6,en;q=0.4Origin: http://webserver:8088User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2376.0 Safari/537.36Host: webserver:8088Accept: application/xml, text/xml, */*; q=0.01X-client: CalDavZAP 0.12.1 (Inf-IT CalDAV Web Client)Connection: keep-aliveContent-length: 723Cookie: agendav_sessid=2f3062c5049a5ec4ab347756128627e4X-requested-with: XMLHttpRequestAuthorization: Basic ...Depth: 0
<?xml version="1.0" encoding="utf-8"?><A:expand-property xmlns:A="DAV:"><A:property name="calendar-proxy-read-for" namespace="http://calendarserver.org/ns/"><A:property name="email-address-set" namespace="http://calendarserver.org/ns/"/><A:property name="displayname" namespace="DAV:"/><A:property name="calendar-user-address-set" namespace="urn:ietf:params:xml:ns:caldav"/></A:property><A:property name="calendar-proxy-write-for" namespace="http://calendarserver.org/ns/"><A:property name="email-address-set" namespace="http://calendarserver.org/ns/"/><A:property name="displayname" namespace="DAV:"/><A:property name="calendar-user-address-set" namespace="urn:ietf:params:xml:ns:caldav"/></A:property></A:expand-property>
----------------------
In config.js
var globalNetworkCheckSettings={href: 'http://webserver:8088/dav/principals/user/', hrefLabel: null, additionalResources: [], forceReadOnly: null, settingsAccount: true, timeOut: 90000, lockTimeOut: 10000, delegation: true, backgroundCalendars: [], ignoreAlarms: false}
------------------
Another idea ?
On Wed, Apr 29, 2015 at 9:56 AM, Ken Murchison <murch@xxxxxxxxxxxxxx> wrote:
On 04/29/2015 08:41 AM, Lucas Zinato Carraro wrote:
How to set document root to dcyrus httpd?
Only put
httpdocroot: /var/lib/cyrus/htdocs ?
in imapd.conf or is necessary to configure another option ?
That's all you need.
On Wed, Apr 29, 2015 at 8:51 AM, Ken Murchison <murch@xxxxxxxxxxxxxx> wrote:
On 04/28/2015 11:27 PM, Lucas Zinato Carraro wrote:
caldavzap is in another server.
Why not just have Cyrus HTTP serve up CalDAVZAP? This will avoid the cross-origin requests the JavasScript is complaining about.
----
I debug more and find this log in _javascript_ console.
XMLHttpRequest cannot load http://mailserver.com:8088/dav/principals/user/. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://webserver.com' is therefore not allowed access.
---
Anyway to put this specific header in cyrus httpd ?
Try setting the httpallowcors option in imap.conf. This should enable the cross-origin headers,
On Mon, Apr 27, 2015 at 8:25 AM, Ken Murchison <murch@xxxxxxxxxxxxxx> wrote:
Have you placed all of the CalDAVZap files in a location within your Cyrus 'htdocs' directory?On 04/17/2015 10:17 AM, Lucas Zinato Carraro wrote:
I'm testing Cyrus Caldav ( 2.4.17+beta9 ) with several clients iCal, Lightning, AgendaDAV, Evolution .
Unfortunately, I could not configure with the CalDavZAP 0.12.1
I follow the procedure to 2.5.0 ( http://cyrusimap.org/docs/cyrus-imapd/2.5.0/install-http.php)
---In cyrus.conf
SERVICES {
..........http cmd="httpd" listen="8088" prefork=0 maxchild=400
.........}
---
In caldav/config.js
var globalNetworkCheckSettings={href: 'http://myserver.com:8088/dav/principals/user/', hrefLabel: null, additionalResources: [], forceReadOnly: null, settingsAccount: true, timeOut: 90000, lockTimeOut: 10000, delegation: true, backgroundCalendars: [], ignoreAlarms: false}
....var globalSettingsType='calendar-home-set';....
Any suggestion ?
Are they readable by the Cyrus user?
Do you have a trailing '/' in the URL when you try to access CalDAVZap (e.g. http://myserver.com:8088/caldavzap/) ?
Are you seeing any kind of errors in syslog?
Have you enabled any kind of logging in your browser?
-- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University
-- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University
-- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University
-- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
