tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kief Morris <>
Subject [PATCH] Jakarta site release page (was: [SECURITY] Security Vulnerabilities in Tomcat 3.1 and 3.2)
Date Tue, 12 Dec 2000 10:01:58 GMT
Hans Bergsten typed the following on 17:39 11/12/2000 -0800
>+0. Is removing TC 3.1 from the download pages an alternative? There shouldn't
>be any reason for anyone to use TC 3.1 now when 3.2 is released. Upgrading to
>3.2.1 could be the recommended action for all TC 3.1 users that need to plug
>the security holes.

This might be a good time to point out that the download page for source code,, has reverted to listing Tomcat
3.1 as "the latest release quality Tomcat build", and doesn't have a link to the 
3.2 final release. It looks like a change to the file yesterday overwrote the new

Here's a patch, although it's probably easier to change by hand. The binaries
page seems ok.

@@ -178,8 +178,8 @@
-<li><a href="/builds/tomcat/release/v3.1/src">Tomcat
-3.1</a> is the latest release quality Tomcat build.</li>
+<li><a href="/builds/tomcat/release/v3.2/src">Tomcat
+3.2</a> is the latest release quality Tomcat build.</li>
 <li><a href="/builds/ant/release/v1.2/src">Ant
 1.2</a> is the latest release of the Ant Subproject.</li>
@@ -189,7 +189,6 @@
-<li><a href="/builds/tomcat/release/v3.2-beta-8/">Tomcat 3.2 beta 8</a></li>
 <li><a href="/builds/jakarta-tomcat-4.0/release/v4.0-m3/">Tomcat 4.0
 milestone 3</a></li>

              bitBull makes the Internet bite:

View raw message