Can't login to account with @ in login



  • When I'm trying to setup carddav account on Owncloud I get error:

      "Missing capabilities, couldn't determine address book home set"
    

    Similar error I got for calendars.

    I found problem connected with the @ symbol in login, when I created account "test" everything was working, but it doesn't seems to be working with account "test@".

    Maybe it is because owncloud suggets me using address https://our.owncloud.address/remote.php/carddav/addressbooks/test%40/contacts (note %40 instead of @)

    It would be great if davdroid would be able to support @'s - in our system user logins and user mails are one thing and I believe that it isn't a strange case.



  • I'm having this issue as well.



  • I'm having this same issue as well, also with owncloud. I captured some logcat output but don't know if it will be helpful or not:

    I/davdroid.QueryServerDialogFragment(11326): onCreateLoader
    I/davdroid.WebDavResource(11326): Using preemptive Basic Authentication
    D/davdroid.HttpPropfind(11326): Prepared PROPFIND request: <propfind xmlns="DAV:">
    D/davdroid.HttpPropfind(11326):    <prop>
    D/davdroid.HttpPropfind(11326):       <current-user-principal/>
    D/davdroid.HttpPropfind(11326):    </prop>
    D/davdroid.HttpPropfind(11326): </propfind>
    W/SingleClientConnManager(11326): Invalid use of SingleClientConnManager: connection still allocated.
    W/SingleClientConnManager(11326): Make sure to release the connection before allocating another one.
    D/davdroid.WebDavCollection(11326): Received multistatus response: <?xml version="1.0" encoding="utf-8"?>
    D/davdroid.WebDavCollection(11326): <d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:card="urn:ietf:params:xml:ns:carddav"><d:response><d:href>/owncloud/remote.php/carddav/</d:href><d:propstat><d:prop><d:current-user-principal><d:href>/owncloud/remote.php/carddav/principals/user@example.org/</d:href></d:current-user-principal></d:prop><d:status>HTTP/1.1 200 OK</d:status></d:propstat></d:response></d:multistatus>
    I/davdroid.ServerInfoLoader(11326): Found principal path: /owncloud/remote.php/carddav/principals/user@example.org/
    D/davdroid.HttpPropfind(11326): Prepared PROPFIND request: <propfind xmlns="DAV:">
    D/davdroid.HttpPropfind(11326):    <prop>
    D/davdroid.HttpPropfind(11326):       <CD:addressbook-home-set xmlns:CD="urn:ietf:params:xml:ns:carddav"/>
    D/davdroid.HttpPropfind(11326):       <C:calendar-home-set xmlns:C="urn:ietf:params:xml:ns:caldav"/>
    D/davdroid.HttpPropfind(11326):    </prop>
    D/davdroid.HttpPropfind(11326): </propfind>
    W/SingleClientConnManager(11326): Invalid use of SingleClientConnManager: connection still allocated.
    W/SingleClientConnManager(11326): Make sure to release the connection before allocating another one.
    D/davdroid.WebDavCollection(11326): Received multistatus response: <?xml version="1.0" encoding="utf-8"?>
    D/davdroid.WebDavCollection(11326): <d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:card="urn:ietf:params:xml:ns:carddav"><d:response><d:href>/owncloud/remote.php/carddav/principals/user%40example.org/</d:href><d:propstat><d:prop><card:addressbook-home-set><d:href>/owncloud/remote.php/carddav/addressbooks/user@example.org/</d:href></card:addressbook-home-set></d:prop><d:status>HTTP/1.1 200 OK</d:status></d:propstat><d:propstat><d:prop><x3:calendar-home-set xmlns:x3="urn:ietf:params:xml:ns:caldav"/></d:prop><d:status>HTTP/1.1 404 Not Found</d:status></d:propstat></d:response></d:multistatus>
    

    If more info is needed, please let me know.


  • admin

    Thank you for reporting this. We'll soon have a look at this!


  • developer

    Fixed with commit db1f2666e8c6148b6ed45d7895ca77697adb24b5. See also https://github.com/owncloud/contacts/issues/222.


  • developer

    In https://github.com/owncloud/contacts/issues/222, @tanghus has backported some fixes that should fix the login with "@" or login with " " problems. If you can test it, please comment there.


Log in to reply
 

Looks like your connection to Bitfire App Forums was lost, please wait while we try to reconnect.