httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-site/xdocs/info/css-security apache_specific.html
Date Wed, 06 Feb 2002 18:49:38 GMT
slive       02/02/06 10:49:38

  Modified:    docs/info/css-security apache_specific.html
               xdocs/info/css-security apache_specific.html
  Log:
  fix typos
  
  Submitted by:	Stas Bekman <stas@stason.org>
  
  Revision  Changes    Path
  1.2       +2 -2      httpd-site/docs/info/css-security/apache_specific.html
  
  Index: apache_specific.html
  ===================================================================
  RCS file: /home/cvs/httpd-site/docs/info/css-security/apache_specific.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -d -b -u -r1.1 -r1.2
  --- apache_specific.html	21 Nov 2001 07:31:46 -0000	1.1
  +++ apache_specific.html	6 Feb 2002 18:49:38 -0000	1.2
  @@ -17,7 +17,7 @@
   <P>While reviewing the Apache code for any problems related to this
   problem, we have discovered a number of issues.  Many of them are
   not bugs in Apache, but are places where Apache can do more to
  -avoid being vulnerable to the Cross Site Scriptint security problem.
  +avoid being vulnerable to the Cross Site Scripting security problem.
   None of the changes fix any security holes in Apache itself that
   can compromise the server directly, but are focused towards its
   interaction with clients.
  @@ -60,7 +60,7 @@
   
   <LI>What is necessary to ensure that sites that legitimately use character
   sets with different encodings of special characters, such as UTF-7, are 
  -protected?  How can Apache facilitate this?  This is a major issue for 
  +protected.  How can Apache facilitate this?  This is a major issue for 
   those with a significant amount of content in character sets other than
   iso-8859-1.
   
  
  
  
  1.2       +2 -2      httpd-site/xdocs/info/css-security/apache_specific.html
  
  Index: apache_specific.html
  ===================================================================
  RCS file: /home/cvs/httpd-site/xdocs/info/css-security/apache_specific.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -d -b -u -r1.1 -r1.2
  --- apache_specific.html	21 Nov 2001 07:16:36 -0000	1.1
  +++ apache_specific.html	6 Feb 2002 18:49:38 -0000	1.2
  @@ -17,7 +17,7 @@
   <P>While reviewing the Apache code for any problems related to this
   problem, we have discovered a number of issues.  Many of them are
   not bugs in Apache, but are places where Apache can do more to
  -avoid being vulnerable to the Cross Site Scriptint security problem.
  +avoid being vulnerable to the Cross Site Scripting security problem.
   None of the changes fix any security holes in Apache itself that
   can compromise the server directly, but are focused towards its
   interaction with clients.
  @@ -60,7 +60,7 @@
   
   <LI>What is necessary to ensure that sites that legitimately use character
   sets with different encodings of special characters, such as UTF-7, are 
  -protected?  How can Apache facilitate this?  This is a major issue for 
  +protected.  How can Apache facilitate this?  This is a major issue for 
   those with a significant amount of content in character sets other than
   iso-8859-1.
   
  
  
  

Mime
View raw message