Baikal: After upgrade from 0.2.7 to 0.4.3 CardDavMATE/InfCloud addressbook view is not working

Created on 26 Mar 2016  路  8Comments  路  Source: sabre-io/Baikal

Hello, I use CardDavMATE with config:

var globalNetworkCheckSettings={
        href: location.protocol+'//'+location.hostname+
                (location.port ? ':'+location.port: '')+
                location.pathname.replace(RegExp('/+[^/]+/*(index\.html)?$'),'')+
                '/card.php/principals/',

line:

                '/dav.php/principals/',

has the same effect.

Request when I log in:

REPORT /card.php/addressbooks/mylogin/default/ HTTP/1.1
Host: ...
User-Agent: ...
Accept: application/xml, text/xml, */*; q=0.01
Accept-Language: en-US,en;q=0.7,pl;q=0.3
Accept-Encoding: gzip, deflate, br
Referer: https://HOST/card.php/addressbooks/mylogin/default/
Content-Type: text/xml; charset=utf-8
Authorization: ...
X-client: CardDavMATE 0.13.1 (Inf-IT CardDAV Web Client)
Depth: 1
X-Requested-With: XMLHttpRequest
Content-Length: 185
Cookie: ...
Connection: keep-alive

Response for that:

HTTP/2.0 415 Unsupported Media Type
...
Content-Type: application/xml; charset=utf-8
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
x-sabre-version: 3.1.2
X-Firefox-Spdy: h2

Address books are listed in CardDavMATE and InfCloud fine.
DAVdroid works fine too.
Calendar sync works great with DAVdroid and InfCloud.

When I'm logged in I can see requests:

PROPPATCH /card.php/principals/mylogin/ HTTP/1.1
Host: HOST
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0
Accept: application/xml, text/xml, */*; q=0.01
Accept-Language: en-US,en;q=0.7,pl;q=0.3
Accept-Encoding: gzip, deflate, br
Referer: https://HOST/card.php/principals/mylogin/
Content-Type: text/xml
Authorization: ...
X-client: CardDavMATE 0.13.1 (Inf-IT CardDAV Web Client)
Depth: 0
X-Requested-With: XMLHttpRequest
Content-Length: 2583
Cookie: ...
Connection: keep-alive

and reply:

HTTP/2.0 403 Forbidden
...
Content-Type: application/xml; charset=utf-8
Vary: Accept-Encoding
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Encoding: gzip
X-Firefox-Spdy: h2
bug

All 8 comments

Are you able to share the response body for the 415 error? The body should contain an xml document with more information about what might be wrong,

Hello, thanks for respond.
There is response body for 415:

<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:sabredav-version>3.1.2</s:sabredav-version>
  <s:exception>Sabre\DAV\Exception\ReportNotSupported</s:exception>
  <s:message/>
  <d:supported-report/>
</d:error>

In that case, are you also able to share the XML document for that REPORT request?

request:

REPORT /dav.php/addressbooks/mylogin/default/ HTTP/1.1
Host: HOSTNAME
User-Agent: ...
Accept: application/xml, text/xml, */*; q=0.01
Accept-Language: en-US,en;q=0.7,pl;q=0.3
Accept-Encoding: gzip, deflate, br
Referer: https://HOSTNAME/dav.php/addressbooks/mylogin/default/
Content-Type: text/xml; charset=utf-8
Authorization: Basic ...
X-client: CardDavMATE 0.13.1 (Inf-IT CardDAV Web Client)
Depth: 1
X-Requested-With: XMLHttpRequest
Content-Length: 185
Cookie: PHPSESSID=...
Connection: keep-alive
<?xml version="1.0" encoding="utf-8"?><D:sync-collection xmlns:D="DAV:"><D:prop><D:getcontenttype/><D:getetag/></D:prop><D:sync-level>1</D:sync-level><D:sync-token/></D:sync-collection>

response:

HTTP/2.0 415 Unsupported Media Type
Server: nginx
Date: Sat, 26 Mar 2016 18:22:13 GMT
Content-Type: application/xml; charset=utf-8
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
x-sabre-version: 3.1.2
X-Firefox-Spdy: h2
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:sabredav-version>3.1.2</s:sabredav-version>
  <s:exception>Sabre\DAV\Exception\ReportNotSupported</s:exception>
  <s:message/>
  <d:supported-report/>
</d:error>

Now I see that after some time calendars have the same issue:
image
Any ideas? timeout? session?

Ok that makes sense. We haven't enabled the sync plugin yet. Enabling this might actually also solve #474 and #518 . I don't think that CardDAVMate is doing the _correct_ thing here, but enabling the sync plugin on our side will make Baikal much faster and fix your problem.

I'm going to add this and try to do a release this weekend somewhere.

I just did a release. I feel that this should solve all your problems. Want to give it a shot?

first impression: works great.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

gitfvb picture gitfvb  路  4Comments

BobWs picture BobWs  路  5Comments

daimaire picture daimaire  路  3Comments

sicherist picture sicherist  路  4Comments

yanngdev picture yanngdev  路  8Comments