From de739c60c03c114e54e35f7d9c4d6deb501b74e0 Mon Sep 17 00:00:00 2001 From: ivanr Date: Wed, 20 Jun 2007 11:17:07 +0000 Subject: [PATCH] Updated documentation for RESPONSE_CONTENT_TYPE and RESPONSE_CONTENT_LENGTH. --- doc/modsecurity2-apache-reference.xml | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/doc/modsecurity2-apache-reference.xml b/doc/modsecurity2-apache-reference.xml index e80ee5a2..a45d5079 100644 --- a/doc/modsecurity2-apache-reference.xml +++ b/doc/modsecurity2-apache-reference.xml @@ -2440,21 +2440,23 @@ SecRule XML "@validateDTD /opt/apache-frontend/conf/xml.dtd"
- <literal>RESPONSE_CONTENT_LENGTH</literal> (Experimental) + <literal>RESPONSE_CONTENT_LENGTH</literal> Response body length in bytes. Can be available starting with phase 3 but it does not have to be (as the length of response body is - not always known in advance.) Does not exist of the content length is - not know. (We will consider making it empty if the size is not - known.) + not always known in advance.) If the size is not known this variable + will contain a zero. If RESPONSE_CONTENT_LENGTH + contains a zero in phase 5 that means the actual size of the response + body was 0. The value of this variable can change between phases if the body - is modified. For example, in embedded mode mod_deflate can compress the - response body between phases 4 and 5. + is modified. For example, in embedded mode + mod_deflate can compress the response body between + phases 4 and 5.
- <literal>RESPONSE_CONTENT_TYPE</literal> (Experimental) + <literal>RESPONSE_CONTENT_TYPE</literal> Response content type. Only available starting with phase 3.