Hi,

Sorry for multiple email. I will be more concise.

It not seems cache problem. Tested with multiple ways:
- Fresh web browser install
- Deletion of all cache in browser
- With setup of apache2 config/.htaccess as said
Same behaviour, not all calendars are displayed.

I attach in this mail (or available at http://sk.bux.fr/~bux/caldavzap/2016-07-29/):
- config.js
- a log of browser output (we can see an clear cache event)
- screenshot of interface with two calendar instead of 5.

Notice calendars urls are:
- http://127.0.0.1:5232/user/1.ics/
- http://127.0.0.1:5232/workspace/2ics/
- http://127.0.0.1:5232/workspace/1.ics/
- http://127.0.0.1:5232/workspace/3.ics/
- http://127.0.0.1:5232/workspace/4.ics/
and displayed calendars are:
- http://127.0.0.1:5232/user/1.ics/
- http://127.0.0.1:5232/workspace/4.ics/
maybe the "/workspace/" common structure of calendars is a problem for caldavzap ?

Regards,
Bastien.



On 28/07/2016 17:27, Ján Máté wrote:
Hi,

next time please do not send 3 emails instead of one ...

You problem is 99% related to browser cache (what is a completely different thing than HTML5 cache).

There is a .htaccess file which adds proper cache headers to files (.js, .html, ...). If .htaccess is not processed
by your HTTP server, then your browser caches the config.js (and all other files including cache.manifest which
is updated by ./cache_update.sh) so the changed files are NOT downloaded by your browser.

You need to:

1.) delete all caches in your browser
2.) set your HTTP server to process the .htaccess file (which correctly sets the cache header => standard browser cache is completely disabled)

and then your config will work (because the client will download the latest source code + config.js) ...


Cheers,


JM


On 28 Jul 2016, at 15:24, Bastien Sevajol <bastien.sevajol@algoo.fr> wrote:

Hi,
After apply the path and execute cache_update.sh, i have similar behaviour:
With these 3 configured calendars:
{
        href: 'http://127.0.0.1:5232/user/1.ics/',
        userAuth:
        {
            userName: 'admin@admin.admin',
            userPassword: 'admin@admin.admin'
        },
        timeOut: 90000,
        lockTimeOut: 10000,
        checkContentType: true,
        settingsAccount: false,
        delegation: false,
        forceReadOnly: null,
        ignoreAlarms: false,
        backgroundCalendars: []
    },
    {
        href: 'http://127.0.0.1:5232/workspace/1.ics/',
        userAuth:
        {
            userName: 'admin@admin.admin',
            userPassword: 'admin@admin.admin'
        },
        timeOut: 90000,
        lockTimeOut: 10000,
        checkContentType: true,
        settingsAccount: false,
        delegation: false,
        forceReadOnly: null,
        ignoreAlarms: false,
        backgroundCalendars: []
    },
    {
        href: 'http://127.0.0.1:5232/workspace/2.ics/',
        userAuth:
        {
            userName: 'admin@admin.admin',
            userPassword: 'admin@admin.admin'
        },
        timeOut: 90000,
        lockTimeOut: 10000,
        checkContentType: true,
        settingsAccount: false,
        delegation: false,
        forceReadOnly: null,
        ignoreAlarms: false,
        backgroundCalendars: []
    },
I have only two calendar displayed (/user/1.ics/ and /workspace/2.ics/). 
Log says 3 calendar are reads:
Info: [userAccount: 'http://admin@admin.admin@127.0.0.1:5232/user/1.ics/']: crossDomain set to: 'true'
main.js:823 Info: [userAccount: 'http://admin@admin.admin@127.0.0.1:5232/workspace/1.ics/']: crossDomain set to: 'true'
main.js:823 Info: [userAccount: 'http://admin@admin.admin@127.0.0.1:5232/workspace/2.ics/']: crossDomain set to: 'true'
I can setup more calendars configs, bahaviour still like that.
I you need more trace/information, i'm listening.

Regards,
Bastien Sevajol.