[turba] 401 Error when accessing via Android client CardDAV-Sync

[Dominik Erdmann]

Hello,

I saw in my Apache logfiles that all my three Android clients enters a
401 (unauthorized) error when they accessing via the client
CardDAV-Sync. See below attached log entries. The first one contains the
error. Conspicuous is that the user name determined by HTTP
authentication is missing.

Now my question: Do you know such entries? Is it possible to avoid these
entries? Is there any option in Horde or the client?

=> The synchronization seems to work fine!
(I'm using latest horde-git)


Thanks,
Dominik



93.231.129.227 - - [29/May/2016:22:04:02 +0200] "OPTIONS
/site/rpc.php/addressbooks/horde-user/contacts~XK5VyHipw66t0odp4aT71ok/
HTTP/1.1" 401 5191 "-" "CardDAV-Sync/0.4.19 (Motorola; cm_osprey;
Android 6.0.1; de_DE; org.dmfs.carddav.Sync/139)"
93.231.129.227 - horde-user [29/May/2016:22:04:02 +0200] "OPTIONS
/site/rpc.php/addressbooks/horde-user/contacts~XK5VyHipw66t0odp4aT71ok/
HTTP/1.1" 200 1067 "-" "CardDAV-Sync/0.4.19 (Motorola; cm_osprey;
Android 6.0.1; de_DE; org.dmfs.carddav.Sync/139)"
93.231.129.227 - horde-user [29/May/2016:22:04:02 +0200] "PROPFIND
/site/rpc.php/addressbooks/horde-user/contacts~XK5VyHipw66t0odp4aT71ok/
HTTP/1.1" 207 1432 "-" "CardDAV-Sync/0.4.19 (Motorola; cm_osprey;
Android 6.0.1; de_DE; org.dmfs.carddav.Sync/139)"
93.231.129.227 - horde-user [29/May/2016:22:04:02 +0200] "PROPFIND
/site/rpc.php/addressbooks/horde-user/contacts~XK5VyHipw66t0odp4aT71ok/
HTTP/1.1" 207 5534 "-" "CardDAV-Sync/0.4.19 (Motorola; cm_osprey;
Android 6.0.1; de_DE; org.dmfs.carddav.Sync/139)"

[Jens Wahnes]

Post by Dominik Erdmann
I saw in my Apache logfiles that all my three Android clients enters a
401 (unauthorized) error when they accessing via the client
CardDAV-Sync. See below attached log entries. The first one contains the
error. Conspicuous is that the user name determined by HTTP
authentication is missing.
Now my question: Do you know such entries? Is it possible to avoid these
entries? Is there any option in Horde or the client?

This is quite normal behavior in both CalDAV and CardDAV. The client
normally does not authenticate to the server unless required. When the
server sends a 401 reply to a request, the client sees the need for
authentication and re-sends the request with authentication information
included.

With this particular client (CardDAV-Sync for Android), you can turn on
"preemptive authentication" in the extended settings. This should get
you rid of the "401" requests because the client will send
authentification information even if the server didn't request it.


Jens

[Dominik Erdmann]

Post by Jens Wahnes

Post by Dominik Erdmann
I saw in my Apache logfiles that all my three Android clients enters a
401 (unauthorized) error when they accessing via the client
CardDAV-Sync. See below attached log entries. The first one contains the
error. Conspicuous is that the user name determined by HTTP
authentication is missing.
Now my question: Do you know such entries? Is it possible to avoid these
entries? Is there any option in Horde or the client?

This is quite normal behavior in both CalDAV and CardDAV. The client
normally does not authenticate to the server unless required. When the
server sends a 401 reply to a request, the client sees the need for
authentication and re-sends the request with authentication information
included.

Okay. I have fears it. :-)

Post by Jens Wahnes
With this particular client (CardDAV-Sync for Android), you can turn on
"preemptive authentication" in the extended settings. This should get
you rid of the "401" requests because the client will send
authentification information even if the server didn't request it.

Great! Thank you for the hint. I will test it.