diff options
author | w0den <w0den@live.com> | 2015-05-11 17:58:20 +0200 |
---|---|---|
committer | w0den <w0den@live.com> | 2015-05-11 17:58:20 +0200 |
commit | dc29c6dc9069650d69496635643f00ab5e52067e (patch) | |
tree | 72248af85a93b258e32df67224804717f201ea3b /user_guide_src/source/libraries/migration.rst | |
parent | 0b978ddf678281ad8c1ab263040fd108be6c926f (diff) |
Improve Cache Query String behaviour
Typically, in most cases, we do not need to cache all the Query String variables. That's why I suggest to improve `Cache Include Query String` behaviour — allow the developer to independently specify which variables should be cached.
For example, consider a query to the following URL address:
http://site.com/search?q=query&page=2&session=abcd&utm_source=web
In this case we don't need to build md5 hash for entire query string, because `session` or `utm_source` can be different for all users. The only variables which should be used for md5 hash should be `q` and `page`. Thus, in `config.php` we can use `$config['cache_query_string'] = array('page', 'q');`.
So:
`$config['cache_query_string'] = FALSE;` → Cache Include Query String is disabled
`$config['cache_query_string'] = TRUE;` → Cache Include Query String is enabled for all
`$config['cache_query_string'] = array('page', 'q');` → enabled only for specified variables
Diffstat (limited to 'user_guide_src/source/libraries/migration.rst')
0 files changed, 0 insertions, 0 deletions