Author: markt
Date: Wed Mar 21 18:55:43 2007
New Revision: 521080

URL: http://svn.apache.org/viewvc?view=rev&rev=521080
Log:
Fix typo.

Modified:
    tomcat/site/trunk/docs/security-4.html
    tomcat/site/trunk/docs/security-5.html
    tomcat/site/trunk/docs/security-6.html
    tomcat/site/trunk/xdocs/security-4.xml
    tomcat/site/trunk/xdocs/security-5.xml
    tomcat/site/trunk/xdocs/security-6.xml

Modified: tomcat/site/trunk/docs/security-4.html
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-4.html?view=diff&rev=521080&r1=521079&r2=521080
==============================================================================
--- tomcat/site/trunk/docs/security-4.html (original)
+++ tomcat/site/trunk/docs/security-4.html Wed Mar 21 18:55:43 2007
@@ -230,7 +230,7 @@
     <p>Requests with multiple content-length headers should be rejected as
        invalid. When multiple components (firewalls, caches, proxies and 
Tomcat)
        process a sequence of requests where one or more requests contain
-       multiple content-length headers and several components accept do not
+       multiple content-length headers and several components do not
        reject the request and make different decisions as to which
        content-length leader to use an attacker can poision a web-cache, 
perform
        an XSS attack and obtain senstive information from requests other then

Modified: tomcat/site/trunk/docs/security-5.html
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-5.html?view=diff&rev=521080&r1=521079&r2=521080
==============================================================================
--- tomcat/site/trunk/docs/security-5.html (original)
+++ tomcat/site/trunk/docs/security-5.html Wed Mar 21 18:55:43 2007
@@ -230,7 +230,7 @@
     <p>Requests with multiple content-length headers should be rejected as
        invalid. When multiple components (firewalls, caches, proxies and 
Tomcat)
        process a sequence of requests where one or more requests contain
-       multiple content-length headers and several components accept do not
+       multiple content-length headers and several components do not
        reject the request and make different decisions as to which
        content-length leader to use an attacker can poision a web-cache, 
perform
        an XSS attack and obtain senstive information from requests other then

Modified: tomcat/site/trunk/docs/security-6.html
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security-6.html?view=diff&rev=521080&r1=521079&r2=521080
==============================================================================
--- tomcat/site/trunk/docs/security-6.html (original)
+++ tomcat/site/trunk/docs/security-6.html Wed Mar 21 18:55:43 2007
@@ -230,7 +230,7 @@
     <p>Requests with multiple content-length headers should be rejected as
        invalid. When multiple components (firewalls, caches, proxies and 
Tomcat)
        process a sequence of requests where one or more requests contain
-       multiple content-length headers and several components accept do not
+       multiple content-length headers and several components do not
        reject the request and make different decisions as to which
        content-length leader to use an attacker can poision a web-cache, 
perform
        an XSS attack and obtain senstive information from requests other then

Modified: tomcat/site/trunk/xdocs/security-4.xml
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-4.xml?view=diff&rev=521080&r1=521079&r2=521080
==============================================================================
--- tomcat/site/trunk/xdocs/security-4.xml (original)
+++ tomcat/site/trunk/xdocs/security-4.xml Wed Mar 21 18:55:43 2007
@@ -32,7 +32,7 @@
     <p>Requests with multiple content-length headers should be rejected as
        invalid. When multiple components (firewalls, caches, proxies and 
Tomcat)
        process a sequence of requests where one or more requests contain
-       multiple content-length headers and several components accept do not
+       multiple content-length headers and several components do not
        reject the request and make different decisions as to which
        content-length leader to use an attacker can poision a web-cache, 
perform
        an XSS attack and obtain senstive information from requests other then

Modified: tomcat/site/trunk/xdocs/security-5.xml
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-5.xml?view=diff&rev=521080&r1=521079&r2=521080
==============================================================================
--- tomcat/site/trunk/xdocs/security-5.xml (original)
+++ tomcat/site/trunk/xdocs/security-5.xml Wed Mar 21 18:55:43 2007
@@ -32,7 +32,7 @@
     <p>Requests with multiple content-length headers should be rejected as
        invalid. When multiple components (firewalls, caches, proxies and 
Tomcat)
        process a sequence of requests where one or more requests contain
-       multiple content-length headers and several components accept do not
+       multiple content-length headers and several components do not
        reject the request and make different decisions as to which
        content-length leader to use an attacker can poision a web-cache, 
perform
        an XSS attack and obtain senstive information from requests other then

Modified: tomcat/site/trunk/xdocs/security-6.xml
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security-6.xml?view=diff&rev=521080&r1=521079&r2=521080
==============================================================================
--- tomcat/site/trunk/xdocs/security-6.xml (original)
+++ tomcat/site/trunk/xdocs/security-6.xml Wed Mar 21 18:55:43 2007
@@ -32,7 +32,7 @@
     <p>Requests with multiple content-length headers should be rejected as
        invalid. When multiple components (firewalls, caches, proxies and 
Tomcat)
        process a sequence of requests where one or more requests contain
-       multiple content-length headers and several components accept do not
+       multiple content-length headers and several components do not
        reject the request and make different decisions as to which
        content-length leader to use an attacker can poision a web-cache, 
perform
        an XSS attack and obtain senstive information from requests other then



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to