Query: proxy cache extend: match content types

[peterbowey]

@InfoHunter

Looking through the debug log for SEnginx, I noted entries with: "proxy cache extend: match content types, caching" (this occurred for a html asset => a 'fastcgi' http upstream request: "/index.php?q=". I note this 'cache_extend' occurred on a 'fastcgi' and not a 'proxy' upstream....

Checking the 'proxy cache extend' notes at the SEnginx Wiki: http://www.senginx.org/en/index.php/Cache_Extend it 'reads' as being only for use with "NGINX Proxy module"

So I assume (by virtue of the debug logs) that 'proxy cache extend' can be applied to both 1) "ngx_http_fastcgi_module" and 2) "ngx_http_proxy_module".

Sorry for the 'noise' - just need to understand the SEnginx "Cache Extend" better.

[InfoHunter]

@peterbowey

Yep, the cache extend feature is designed for proxy module. But due to the non-perfect implementation, it also affects all fastcgi/uwsgi/scgi... module. And by default, it will only cache "text/html" content. So at current stage, if you use fastcgi cache, please use "proxy_cache_types" directive to set the MIME types that could be cached. The MIME types set by this directive affect all proxy/fastcgi/scgi... module in a same location.

This looks strange. I should implement the cache extend feature into "proxy_cache_types/fastcgi_cache_types/scgi_cache_types" directive sets.

[InfoHunter]

So the configuration might be like this:

location /xxxxxx {
    fastcgi_cache some_cache;
    ...
    proxy_cache_types text/html aaa/bbb ccc/ddd eee/fff;
    ...
    fastcgi_pass abcdefghijklmn;
}

: )

[peterbowey]

@InfoHunter

Thanks, above excerpt make sense (now).

Reads much 'nicer' when you can apply; 1) "proxy_cache_types,
2) fastcgi_cache_types, and 3)scgi_cache_types" directive sets via cache extend...

[InfoHunter]

@peterbowey

New fastcgi_cache_type is added, so the proxy_cache_types now only affects proxy module.

have a look at: adf89f4

And the documentation is also updated.