Re: Configure Cyrus 2.4.17+caldav~beta9 and CalDavZAP 0.12.1

Ken Murchison <murch@xxxxxxxxxxxxxx> · Wed, 29 Apr 2015 07:51:26 -0400



    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:

          
                  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 ?
                      

              Have you placed all of the CalDAVZap files in a location
              within your Cyrus 'htdocs' directory?  

              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

  
----
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