if have GET / POST vars we don't want to trigger the cache redirect
the nginx version is untested
apache might have to be changed depending on what nginx adds in the proxy pass
a model to allow rules to apply to the cache
when rewriting this will allow us to specify a rule set of things to exclude from cache
eg. a basket listing we would not want to cache and always be dynamic, so this would stop it from being written
Merge these in to a single model and give a sensible name
move the lookup checks to this as well
rename a couple of the functions to drop cache prefix as the class name includes that
fix the class names being called to match new version
check to see if the mapping class has been defined, if not find it. Then add a new column to the model to track the location of the cached file.
function name was already in use..
also check & update the saved cache file location on the model (this will be used in the cms listing area)
updated for function name changes
updated readme
rename controllers
use the defined var
register the module for the cms