You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by jw...@apache.org on 2003/11/24 07:17:33 UTC
cvs commit: httpd-site/docs index.html
jwoolley 2003/11/23 22:17:33
Modified: xdocs index.xml
docs index.html
Log:
Add a note about the usertrack borkenness.
Revision Changes Path
1.50 +22 -0 httpd-site/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/httpd-site/xdocs/index.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -u -r1.49 -r1.50
--- index.xml 29 Oct 2003 14:50:25 -0000 1.49
+++ index.xml 24 Nov 2003 06:17:33 -0000 1.50
@@ -37,6 +37,28 @@
your downloads using PGP or MD5 signatures!</p>
</section>
+<section id="bugnotice">
+<title>Important Bug Workaround for 2.0.48 and 1.3.29</title>
+
+<p>If you use mod_usertrack with the default
+<a href="http://httpd.apache.org/docs-2.0/mod/mod_usertrack.html#cookiename">CookieName</a> (ie, there is no CookieName directive in your config file), then
+you will encounter a bug in 2.0.48 and 1.3.29.
+</p>
+
+<p>The patch that was added to these versions to help prevent false-positive
+matches of the CookieName did not take into account this case, and therefore
+the regular expression that is now used in the matching process will be NULL
+if no CookieName directive was encountered.</p>
+
+<p>This problem will be fixed in both 2.0.49 and 1.3.30 when they are
+released. As a simple workaround in 2.0.48 and 1.3.29, simply add the
+line<br />
+<code>CookieName Apache</code><br />
+to your config file. (While you're at it, you could pick a more
+meaningful cookie name than "Apache", but any cookie name will do.)
+</p>
+</section>
+
<section id="2.0.48">
<title>Apache 2.0.48 Released</title>
1.68 +26 -0 httpd-site/docs/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/httpd-site/docs/index.html,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -d -u -r1.67 -r1.68
--- index.html 20 Nov 2003 15:49:36 -0000 1.67
+++ index.html 24 Nov 2003 06:17:33 -0000 1.68
@@ -94,6 +94,32 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="bugnotice"><strong>Important Bug Workaround for 2.0.48 and 1.3.29</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+<p>If you use mod_usertrack with the default
+<a href="http://httpd.apache.org/docs-2.0/mod/mod_usertrack.html#cookiename">CookieName</a> (ie, there is no CookieName directive in your config file), then
+you will encounter a bug in 2.0.48 and 1.3.29.
+</p>
+<p>The patch that was added to these versions to help prevent false-positive
+matches of the CookieName did not take into account this case, and therefore
+the regular expression that is now used in the matching process will be NULL
+if no CookieName directive was encountered.</p>
+<p>This problem will be fixed in both 2.0.49 and 1.3.30 when they are
+released. As a simple workaround in 2.0.48 and 1.3.29, simply add the
+line<br />
+<code>CookieName Apache</code><br />
+to your config file. (While you're at it, you could pick a more
+meaningful cookie name than "Apache", but any cookie name will do.)
+</p>
+ </blockquote>
+ </td></tr>
+</table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
<a name="2.0.48"><strong>Apache 2.0.48 Released</strong></a>
</font>
</td></tr>