Mailing-List: contact apache-cvs-help@apache.org; run by ezmlm
Delivered-To: mailing list apache-cvs@apache.org
Received: (qmail 33119 invoked by uid 500); 25 Feb 2000 17:14:06 -0000
Delivered-To: apmail-apache-site-cvs@apache.org
Received: (qmail 33116 invoked by uid 1078); 25 Feb 2000 17:14:06 -0000
Date: 25 Feb 2000 17:14:06 -0000
Message-ID: <20000225171406.33115.qmail@locus.apache.org>
From: jim@locus.apache.org
To: apache-site-cvs@apache.org
Subject: cvs commit: apache-site/info/css-security index.html

jim         00/02/25 09:14:05

  Modified:    info/css-security index.html
  Log:
  Adjust the patch information
  
  Revision  Changes    Path
  1.3       +4 -9      apache-site/info/css-security/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/apache-site/info/css-security/index.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- index.html	2000/02/03 05:16:04	1.2
  +++ index.html	2000/02/25 17:14:05	1.3
  @@ -93,15 +93,10 @@
   
   <UL>
   <LI><A HREF="apache_specific.html">Apache HTTP server specific information</A>
  -
  -<LI>Current <A HREF="apache_1.3.11_css_patch.txt">Apache patch</A> against
  -1.3.11 that addresses the known issues in Apache and provides some help
  -to Apache users in protecting against certain instances of this problem.
  -Please see the previous document for a description of what this patch does.
  -As of the writing of this document, we have not yet released a new version
  -of Apache that includes these patches.  We expect to do so in the near
  -future, once we are more confident that we have addressed all the issues.
  -
  +<LI>Apache 1.3.12, which provides some protection against certain instances of
  + this problem.
  +<LI>Older <A HREF="apache_1.3.11_css_patch.txt">Apache patch</A> against
  +1.3.11 that addressed the known issues in that version of Apache.
   <LI><A HREF="encoding_examples.html">Encoding Examples</A> page, describing
   how to properly encode your output to protect against this problem using
   common Apache related technologies, such as Apache modules, Perl,