Hi Attila,
thanks for your attachment. The reason why you don't see your to-do from last year is because we use time range filtering for todo/event loading (Calendar-query) to minimalize server traffic. So we are loading todos which are after start of that time range. Unfortunately there is no such thing as using of time range filter in combination with STATUS=NEEDS-ACTION filter in logical "OR" relation (http://tools.ietf.org/html/rfc4791#section-7.8).
But you can extend the start of your time range by setting  globalEventStartPastLimit variable to bigger number in config.js file. Default value is 3.
Dňa 22. 4. 2014 22:06 Attila Asztalos wrote / napísal(a):
Unfortunately I don't think I can do that, Baikal only supports digest auth AFAIK. That's the source of all those 401's - they are normal. And, to be honest, best I can tell I never even used a VM before - so this flies a bit over my head. However, I did capture the initial transactions using Chrome - both requests and replies, including the actual XML data. I'll send them to you directly, let me know if they are of any use.

- Attila

On 22-Apr-2014 21:35, Ján Máté wrote:
Unfortunately this information is not really helpful because there are lot of errors (and lot of them are maybe related to digest auth). So my first recommendation is to switch to basic auth (with https). 

For further debugging we really need an access to test server where we can reproduce the problem ... can you create a VMWare virtual machine with minimal Debian installation and Baikal where the problem is reproducible?


On 22 Apr 2014, at 20:09, Attila Asztalos <attila.asztalos@gmail.com> wrote:

Hi Ján,

I'd love to, but this is a home/personal LAN-only server running on my desktop (whenever I start it), not set up to be accessed from the internet - I don't even have a fixed IP. That said, the server I use is Baikal (with digest auth), the Apache log entries between me logging in and the two todo items showing up are pasted below, and I'd be glad to send you / sniff any other traffic you might find useful - just let me know how else I can help...

- Attila

[22/Apr/2014:20:47:03 +0300] "PROPFIND /cal.php/principals/ HTTP/1.1" 401 292
[22/Apr/2014:20:47:04 +0300] "PROPFIND /cal.php/principals/ HTTP/1.1" 207 436
[22/Apr/2014:20:47:04 +0300] "PROPFIND /cal.php/principals/myuser/ HTTP/1.1" 401 292
[22/Apr/2014:20:47:04 +0300] "PROPFIND /cal.php/principals/myuser/ HTTP/1.1" 207 978
[22/Apr/2014:20:47:04 +0300] "PROPFIND /cal.php/calendars/myuser/ HTTP/1.1" 401 292
[22/Apr/2014:20:47:04 +0300] "PROPFIND /cal.php/calendars/myuser/ HTTP/1.1" 207 5218
[22/Apr/2014:20:47:04 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 401 292
[22/Apr/2014:20:47:05 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 207 15309
[22/Apr/2014:20:47:05 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 401 292
[22/Apr/2014:20:47:05 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 207 187
[22/Apr/2014:20:49:04 +0300] "PROPFIND /cal.php/principals/myuser/ HTTP/1.1" 401 292
[22/Apr/2014:20:49:04 +0300] "PROPPATCH /cal.php/principals/myuser/ HTTP/1.1" 401 292
[22/Apr/2014:20:49:05 +0300] "PROPFIND /cal.php/principals/myuser/ HTTP/1.1" 207 978
[22/Apr/2014:20:49:05 +0300] "PROPPATCH /cal.php/principals/myuser/ HTTP/1.1" 403 540
[22/Apr/2014:20:49:05 +0300] "PROPFIND /cal.php/calendars/myuser/ HTTP/1.1" 401 292
[22/Apr/2014:20:49:05 +0300] "PROPFIND /cal.php/calendars/myuser/ HTTP/1.1" 207 5218
[22/Apr/2014:20:49:05 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 401 292
[22/Apr/2014:20:49:05 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 403 275
[22/Apr/2014:20:49:05 +0300] "PROPFIND /cal.php/calendars/myuser/default/ HTTP/1.1" 401 292
[22/Apr/2014:20:49:05 +0300] "PROPFIND /cal.php/calendars/myuser/default/ HTTP/1.1" 207 18026
[22/Apr/2014:20:49:05 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 401 292
[22/Apr/2014:20:49:05 +0300] "REPORT /cal.php/calendars/myuser/default/ HTTP/1.1" 207 27535