Hi,

It will be good if we don't bootstrap drupal totally when serving authenticated cache pages. Like varnish support already built in as a separate authcache backend module.

Any chance that nginx fastcgi cache will be supported?

https://www.digitalocean.com/community/tutorials/how-to-setup-fastcgi-ca...

cheers
dropchew

Comments

dropchew’s picture

dropchew commented
Issue summary: View changes
znerol’s picture

znerol commented
Parent issue: » #2358775: SSI Support

I expect the tricky part to be the nginx configuration. The problem is that the authcache key needs to be part of the fastcgi_cache_key. Imagine something like the following:

fastcgi_cache_key "$scheme$request_method$authcache_key$request_uri";

In the past I've tried several methods to maintain the authcache key for a user. In earlier versions the key was always set as a cookie in the users browser. Authcache Boost still uses that method. I think that this would be relatively easy to implement in nginx config. It would be necessary to sanitize the cookie value (either by comparing it to a list of possible values or with a regex) and then set the $authcache_key variable to the sanitized value. If it is empty or invalid, set it to $host.

The second approach is to always execute two requests, the first fetches the key and the second the page. Obviously the first request will be cached in most cases. This is what is implemented in the VCL and by Authcache Varnish. If it is possible to initiate cacheable HTTP request from nginx config, then this would also be an option.

Another thing to consider is how to expire pages from the Nginx fastcgi cache. If a user posts a comment, the affected page needs to be removed from the cache. This would be the equivalent of the ban command in Varnish. Is there something like that in Nginx?

dropchew’s picture

dropchew commented

Another thing to consider is how to expire pages from the Nginx fastcgi cache. If a user posts a comment, the affected page needs to be removed from the cache. This would be the equivalent of the ban command in Varnish. Is there something like that in Nginx?

Yes its possible using nginx compiled with nginx cache purge module (https://github.com/FRiCKLE/ngx_cache_purge) or the custom method mentioned in https://www.digitalocean.com/community/tutorials/how-to-setup-fastcgi-ca...

I have managed to set a separate cache for each login session using the below. But not sure how can it be integrated with authcache

nginx conf

## Set a cache_uid variable for authenticated users.
map $http_cookie $cache_uid {
        default 0;
        ~SESS[[:alnum:]]+=(?<session_id>[[:alnum:]]+ $cache_uid) ;
}

fastcgi_cache_key "$cache_uid$scheme$request_method$host$request_uri";
cromulus’s picture

cromulus commented

the ngx_cache_purge module isn't needed.

As long as you know the key used to create the cache, you can purge directly using php:

see here:
https://github.com/rtCamp/nginx-helper/blob/master/purger.php

znerol’s picture

znerol commented
Status: Active » Closed (won't fix)