Remove description of transformation caching issues from CHANGES.

This commit is contained in:
ivanr
2008-07-31 09:04:05 +00:00
parent 58c8845f78
commit 2f6d1f873e

22
CHANGES
View File

@@ -1,24 +1,20 @@
28 Jul 2008 - 2.5.6 31 Jul 2008 - 2.5.6
------------------- -------------------
* Transformation caching is now off by default as it may not be appropriate * Transformation caching has been deprecated, and is now off by default. We
in all environments. now advise against using transformation caching in production.
* Fixed an issue with transformation cache using the original value * Fixed two separate transformation caching issues that could cause incorrect
when the last transformation in a chain did not modify the value. This content inspection in some circumstances.
fixes the potential match failure due to a failed transformation.
* Fixed an issue with transformation cache where only the first of duplicate
values in a collection was inspected. This fixes the potential of missing
a duplicate target value for inspection.
* Fixed an issue with the transformation cache using too much RAM, potentially * Fixed an issue with the transformation cache using too much RAM, potentially
crashing Apache with a large number of cache entries. To better control crashing Apache with a large number of cache entries. To new configuration
caching, two new options have been added: options have been added to allow for a finer control of caching:
maxitems: Max number of items to cache (default 1024) maxitems: Max number of items to cache (default 1024)
incremental: Whether to cache incrementally (default off) incremental: Whether to cache incrementally (default off)
* Added an experimental regression testing suite. The regression suite may * Added an experimental regression testing suite. The regression suite may
be executed via "make test-regression", however it is strongly advised be executed via "make test-regression", however it is strongly advised
to only be executed on a non-production machine as it will startup the to only be executed on a non-production machine as it will startup the
Apache web server that ModSecurity is compiled against with various Apache web server that ModSecurity is compiled against with various