server response invalid with assumed correct url

  • xenek

    (@xenek)


    5 years ago

    Hi,

    using latest plugin on latest wordpress

    ERROR: Your Server’s response is invalid and cannot be parsed – please enable Logging and check the Logfile !

    Log created on 19:11:04 10:27:00
CalendarURL:https://server/cal.php/calendars/nwt/default/
<?xml version="1.0"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="https://sabredav.org/ns" xmlns:cal="urn:ietf:params:xml:ns:caldav" xmlns:cs="https://calendarserver.org/ns/"/>Tag://cal:calendar-data
<?xml version="1.0"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="https://sabredav.org/ns" xmlns:cal="urn:ietf:params:xml:ns:caldav" xmlns:cs="https://calendarserver.org/ns/"/>

    Seems like the calendar url is wrong? username in baikal docker container is nwt, calendar token id is default, auth set to basic

    I can bring up the page in browser (follows)

    Nodes
Properties
d:principal-collection-set	/cal.php/principals/
d:current-user-principal	/cal.php/principals/nwt/
d:supported-privilege-set	

    d:all
        d:read
            d:read-acl
            d:read-current-user-privilege-set
            cal:read-free-busy
        d:write
            d:write-properties
            d:write-content
            d:unlock
            d:bind
            d:unbind
            d:write-acl
        d:share

d:current-user-privilege-set	cal:read-free-busy, d:read, d:read-acl, d:read-current-user-privilege-set, d:write-properties, d:write, d:write-content, d:unlock, d:bind, d:unbind, d:write-acl, d:share
d:acl	
Principal	Privilege	
/cal.php/principals/nwt	d:share	(protected)
/cal.php/principals/nwt/calendar-proxy-write	d:share	(protected)
/cal.php/principals/nwt	d:write	(protected)
/cal.php/principals/nwt/calendar-proxy-write	d:write	(protected)
/cal.php/principals/nwt	d:write-properties	(protected)
/cal.php/principals/nwt/calendar-proxy-write	d:write-properties	(protected)
/cal.php/principals/nwt	d:read	(protected)
/cal.php/principals/nwt/calendar-proxy-read	d:read	(protected)
/cal.php/principals/nwt/calendar-proxy-write	d:read	(protected)
d:authenticated	cal:read-free-busy	(protected)
d:owner	/cal.php/principals/nwt/
cs:invite	

 <cs:user>
  <cs:invite-accepted/>
  <cs:access/>
  <d:href>/cal.php/</d:href>
 </cs:user>

d:share-access	

 <d:not-shared/>

d:invite	

 <d:sharee>
  <d:href>/cal.php/</d:href>
  <d:prop/>
  <d:share-access>
   <d:not-shared/>
  </d:share-access>
  <d:invite-accepted/>
 </d:sharee>

d:share-resource-uri	/ns/share/1
cal:max-resource-size	10000000
cal:supported-calendar-data	

 <cal:calendar-data content-type="text/calendar" version="2.0"/>
 <cal:calendar-data content-type="application/calendar+json"/>

cal:supported-collation-set	

 <cal:supported-collation>i;ascii-casemap</cal:supported-collation>
 <cal:supported-collation>i;octet</cal:supported-collation>
 <cal:supported-collation>i;unicode-casemap</cal:supported-collation>

d:sync-token	https://sabre.io/ns/sync/1
d:supported-report-set	d:expand-property, d:principal-match, d:principal-property-search, d:principal-search-property-set, d:sync-collection, cal:calendar-multiget, cal:calendar-query, cal:free-busy-query
d:resourcetype	d:collection, cal:calendar
cs:getctag	1
s:sync-token	1
cal:supported-calendar-component-set	

 <cal:comp name="VEVENT"/>

cal:schedule-calendar-transp	

 <cal:opaque/>

d:displayname	default
cal:calendar-description	Default calendar
cal:calendar-timezone	
{https://apple.com/ns/ical/}calendar-order	0
{https://apple.com/ns/ical/}calendar-color	
cs:allowed-sharing-modes	

 <cs:can-be-shared/>

    Lastly, does this plugin list look right?

    core	The Core plugin provides a lot of the basic functionality required by WebDAV, such as a default implementation for all HTTP and WebDAV methods.	
auth	Generic authentication plugin	
acl	Adds support for WebDAV ACL (rfc3744)	
browser	Generates HTML indexes and debug information for your sabre/dav server	
property-storage	This plugin allows any arbitrary WebDAV property to be set on any resource.	
sync	Adds support for WebDAV Collection Sync (rfc6578)	
caldav	Adds support for CalDAV (rfc4791)	
ics-export	Adds the ability to export CalDAV calendars as a single iCalendar file.	
caldav-schedule	Adds calendar-auto-schedule, as defined in rfc6638	
sharing	This plugin implements WebDAV resource sharing	
caldav-sharing	Adds support for caldav-sharing.	
imip	Email delivery (rfc6047) for CalDAV scheduling

    Any ideas or tips? I’d love to see this work! (Baikal from dockerhub image ckulka/baikal:latest )

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author hoernerfranz

    (@hoernerfranz)

    It looks like your calendar URL is wrong.
    the server’s answer should contain lines like

    <?xml version="1.0"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="https://sabredav.org/ns" xmlns:cal="urn:ietf:params:xml:ns:caldav" 
.
.
.
    <d:getetag>&quot;1f2f2782da2a653f747ca9e81a2c0d75&quot;</d:getetag>
    <cal:calendar-data>BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
-

    which means it should contain lines with ICAL syntax.

    so, I guess, wrong URL or your server does not understand the ‘REPORT’ request.
    however, baikal/sabre dav does that ??

    I propose you try caldav2ics for debugging/verification purpose until you get a valid ics file from you baikal calendar.

    Thread Starter xenek

    (@xenek)

    Ok, thanks! I’ll give it a go. I’ve struggled to identify what the actual caldav url for Baikal should be, so I’m not even sure if Baikal is running properly and fully – even though I have html access to it and that looks fine.

    Plugin Author hoernerfranz

    (@hoernerfranz)

    well, identifying the correct calendar URL seems to be mostly the main reason for not getting the plugin to work ?? .
    for my own baikal implementation, it corresponds to the following scheme:
    <SERVER>/baikal/html/dav.php/calendars/<username>/<calendartoken>

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘server response invalid with assumed correct url’ is closed to new replies.