Feature #2009
Provide config to avoid lastView parameter
| Status: | New | Start: | 02/23/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Configuration | |||
| Target version: | 1.5.0 |
Description
The lastView parameter can lead to a fast growing cache hash table and creates high load on a server when a search engine crawls through the same out multiple times because of different URLs.
Thus, a common workaround is to move lastView to sessionPiVars and to replace all "back" links by a javascript:history.back() call.
I think we should
- provide a configuration option for this and maybe even enable it by default
- try to find another solution without relying on JS.
History
Updated by Markus Drexelius 10 months ago
I support this feature request. We have big problems with cal within our installation: the server performance is extremley high. The cache_pages table is growing to more than 3GB (!) in a few days. Please implement a solution to decrease the needed webserver performance. And please think about an implementation into the 1.4 release. Thanks!
