[Tickets #13449] Re: CalDAV / CardDAV sync need multiple logins / session to work

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/13449
------------------------------------------------------------------------------
  Ticket           | 13449
  Aktualisiert Von | info at gutentag.ch
  Zusammenfassung  | CalDAV / CardDAV sync need multiple logins / session to
                   | work
  Warteschlange    | Horde Groupware Webmail Edition
  Version          | 5.2.1
  Typ              | Bug
  Status           | Feedback
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


info at gutentag.ch (2014-09-22 16:28) hat geschrieben:

I don'ts follow this topic.. and just did one click too early.

The TCP "Ground" Connection is established (libcurl), and of course  
every request has the correct Authentication Header (Basic Realm).  
Also the cookies between requests are treated automatically and  
correctly (same with WinHttp.dll and WinInet.dll).

It's a Kronolith <-> SabreDAV bug, where a second request always fails.
A next HTTP request is only possible, if the TCP connection is closed  
and a new one created (a new handshake for SSL needed).

This issue is also with the demo.horde.org

I don't know the internas of Horde about sessions.
I just can't understand, why Michael is writing about "transparent  
auth" and why "IMP" is mentioned?! Gibberish..

Horde is the only web solution with this special issue. There must be  
something wrong. Smartphones probably use always new connections, but  
e.g. the autodiscover of CalDAV server collections may fail.