Hi there! I set a LDAP (AD) backed user source (acts as both authenticator and global addressbook). There is 222 contacts.
It works kinda fine in SOGo's web interface (all of them appear almost immediatelly, but I facing strange issues when trying to access addressbook through https://my_sogo/SOGo/dav/mva/Contacts/directory/ ("directory" is the ID), I see sogo takes too much time to respond. When client application (or me using cURL) send initial PROPFIND request on that URI, initially it takes sogo ~13 seconds to respond with corresponding XML. But even if I cache this reply, then client makes REPORT-type request to that URI, and it makes sogo worker to freeze and out after 2 minutes (120 secs) and throw 401 error (at least, accouring to SOGo log). The intersting thing is that if I try to manualy get users listing with ldapsearch - it takes about a second (-ish)... SOGo's web-interface also renders users list immediately... But somewhy DAV interface behaves in such a strange way. Can you, please, advice me: 1) is it any way to increase sogo timeout (maybe it's internal timeout of 2 minutes is just not enough for it to perform some tasks)? 2) will some of debug options from config example be useful to try to get information about the reasons of sogo to getting so much time to reply? Or maybe there is some another way to debug that? 3) or maybe I faced some known issue and there is a well-known easy fix for that (that I failing to find myself)? 4) or should I search issues somewhere else? (inb4: there are no overload issues neither on sogo host, nor on DB, nor on AD) Thanks in advance!
