Mmm, I am checking, but I do not think nginx uses .htaccess file...

On 10/30/2015 10:53 AM, Ján Máté wrote:

Maybe your nginx not sends proper cache headers (see the .htaccess file) and your browser (or proxy) use "standard cache" in addition of HTML5 cache.

The cache headers in .htaccess MUST BE USED to prevent additional caching (except the HTML5 cache). Your only solution is to delete your browser local cache (and force expire all caches on proxies if you use any).

JM

...

On 30 Oct 2015, at 10:49, Pierre Couderc pierre@couderc.eu wrote:

I have overinstalled Caldavzap 0.13.1 (my files are dates sept 22 15:30) on a (nice) no config davical/caldavzap installation. And all seems to work except I still have the message inviting to install "0.13.1 (you have0.12.1)". I have restarted nginx, chash_update.sh....

What do I miss...?

Thnak you PC

In nginx access.log, I see : GET /caldavzap/cache_handler.js HTTP/1.1" 200 2267 "https://davical.couderc.eu/caldavzap/" "Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.3.0"

but no request for cache.manifest. So the question seems to me : why the browser does not look for cache.manifest ...?

On 10/30/2015 10:53 AM, Ján Máté wrote:

Maybe your nginx not sends proper cache headers (see the .htaccess file) and your browser (or proxy) use "standard cache" in addition of HTML5 cache.

The cache headers in .htaccess MUST BE USED to prevent additional caching (except the HTML5 cache). Your only solution is to delete your browser local cache (and force expire all caches on proxies if you use any).

JM

...

On 30 Oct 2015, at 10:49, Pierre Couderc pierre@couderc.eu wrote:

I have overinstalled Caldavzap 0.13.1 (my files are dates sept 22 15:30) on a (nice) no config davical/caldavzap installation. And all seems to work except I still have the message inviting to install "0.13.1 (you have0.12.1)". I have restarted nginx, chash_update.sh....

What do I miss...?

Thnak you PC

Thank you, so I try the nginx directive :

add_header Cache-Control "max-age=0, must-revalidate, no-cache, no-transform, private";

On 10/30/2015 05:27 PM, Ján Máté wrote:

Because your server previously returned wrong cache header (instead of the one configured in .htaccess) and your browser cached the cache.manifest?

JM

...

On 30 Oct 2015, at 5:01 PM, Pierre Couderc pierre@couderc.eu wrote:

In nginx access.log, I see : GET /caldavzap/cache_handler.js HTTP/1.1" 200 2267 "https://davical.couderc.eu/caldavzap/" "Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.3.0"

but no request for cache.manifest. So the question seems to me : why the browser does not look for cache.manifest ...?

...

On 10/30/2015 10:53 AM, Ján Máté wrote: Maybe your nginx not sends proper cache headers (see the .htaccess file) and your browser (or proxy) use "standard cache" in addition of HTML5 cache.

The cache headers in .htaccess MUST BE USED to prevent additional caching (except the HTML5 cache). Your only solution is to delete your browser local cache (and force expire all caches on proxies if you use any).

JM

...

On 30 Oct 2015, at 10:49, Pierre Couderc pierre@couderc.eu wrote:

I have overinstalled Caldavzap 0.13.1 (my files are dates sept 22 15:30) on a (nice) no config davical/caldavzap installation. And all seems to work except I still have the message inviting to install "0.13.1 (you have0.12.1)". I have restarted nginx, chash_update.sh....

What do I miss...?

Thnak you PC

Hi,

On 30 Oct 2015, at 18:52, Pierre Couderc pierre@couderc.eu wrote:

Well I have tried to add the nginx directive :

add_header Cache-Control "max-age=0, must-revalidate, no-cache, no-transform, private";

Then clears the browser cache, then it loads 0.13.1, then I reset manifest with ./cache_update.sh and now it accesses too "cache.manifest", so I think it is ok for 0.13.2.

Do I miss someting...?

if the header is sent (I never used nginx so I don't know the configuration options) then everything is OK :-)

JM

PC

In case it may be useful here is my davical, caldavzap, carddavmate nginx server :

#### serveur davical server { server_name davical.couderc.eu davical.secours.couderc.eu; root /usr/share/davical/htdocs; index index.html index.htm index.php index.pl; # begin : https section listen 443; ssl on; ssl_certificate /etc/ssl/pcouderc/certs/davical.couderc.eu.chain.cert.pem; ssl_certificate_key /etc/ssl/pcouderc/private/davical.couderc.eu.key.pem;

ssl_session_timeout 5m;

ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers "HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES"; ssl_prefer_server_ciphers on; # end : https section keepalive_timeout 0; location /images/ { } location / { try_files $uri $uri/ =404; } location ~ ^(.+.php)(.*)$ { include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_pass unix:/tmp/php.socket;

   fastcgi_split_path_info ^(.+\.php)(.*)$;
   fastcgi_param PATH_INFO $fastcgi_path_info;
   fastcgi_param PATH_TRANSLATED $document_root$fastcgi_path_info;

   fastcgi_read_timeout 180;
   fastcgi_buffers 4 256k;
   fastcgi_buffer_size 128k;

}

location ~ .php$ { fastcgi_pass unix:/tmp/php.socket; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include /etc/nginx/fastcgi_params; } location /caldavzap/ {

   add_header Cache-Control "max-age=0, must-revalidate, no-cache, no-transform, private";

} location /carddavmate/ {

   add_header Cache-Control "max-age=0, must-revalidate, no-cache, no-transform, private";

}

}