marcsaeg 01/05/07 18:31:20
Modified: . Tag: tomcat_32 RELEASE-NOTES
src/doc Tag: tomcat_32 readme
Log:
Updated descriptions in section 4, added note about AJP12/SSL limitation
to section 6 and added description of fix for bug 208.
Revision Changes Path
No revision
No revision
1.1.2.7 +19 -3 jakarta-tomcat/Attic/RELEASE-NOTES
Index: RELEASE-NOTES
===================================================================
RCS file: /home/cvs/jakarta-tomcat/Attic/RELEASE-NOTES,v
retrieving revision 1.1.2.6
retrieving revision 1.1.2.7
diff -u -r1.1.2.6 -r1.1.2.7
--- RELEASE-NOTES 2001/05/07 13:34:25 1.1.2.6
+++ RELEASE-NOTES 2001/05/08 01:31:17 1.1.2.7
@@ -1,4 +1,4 @@
-$Id: RELEASE-NOTES,v 1.1.2.6 2001/05/07 13:34:25 marcsaeg Exp $
+$Id: RELEASE-NOTES,v 1.1.2.7 2001/05/08 01:31:17 marcsaeg Exp $
Release Notes for:
====================
@@ -70,9 +70,14 @@
version 3.1 also focused on reorganizing the code (modularization, cleanup,
refactoring, removal of dead code, and separation of J2EE-specific code).
-- Tomcat 3.2 is the first performance tune-up, and also adds a few new
-features (see next section).
+- Tomcat 3.2 was the first performance tune-up, and also added a few new
+features.
+- Tomcat 3.2.1 was a security update. See section 7.3 for details.
+
+- Tomcat 3.2.2 is a bug fix release. Section 7.1 describes the issues
+that have been fixed in the version.
+
- Tomcat 4.0 is separate development from Tomcat 3.x. It is based on the
Catalina architecture, which is very different from the architecture of
Tomcat 3.x. In addition, Tomcat 4.0 is to be the reference implementation
@@ -281,6 +286,15 @@
javax.servlet.Context.getResrouceAsStream() cannot contain URL escapes of
the form %HH. Paths containing any URL escapes will return null.
+6.11 AJP12 and SSL
+
+The AJP12 protocol does not provide a mechanism for identifying requests
+that arrived on a secure transport (e.g. SSL). Tomcat assumes that any
+request that arrived on server port 443 is secure and sets the URL scheme
+to HTTPS. Requests on any other port are assumed to be non-secure and
+will indicate a URL scheme of HTTP. The AJP13 protocol does not suffer
+from this problem.
+
===============================================================================
7. FIXES AND ENHANCEMENTS IN UPDATES
@@ -318,6 +332,8 @@
- HttpServletRequest.encodeURL() now properly encodes URLs that contain
an anchor but no query string. (#1182)
- Error pages now work in virtual hosts.
+ - ServletRequest.getRemoteHost() now returns the remote IP address
+ if the remote host name isn't known. (#208)
Jasper
- Fix for UnsupportedEncodingException due to UTF8 instead of UTF-8. (#269)
No revision
No revision
1.8.2.19 +19 -3 jakarta-tomcat/src/doc/readme
Index: readme
===================================================================
RCS file: /home/cvs/jakarta-tomcat/src/doc/readme,v
retrieving revision 1.8.2.18
retrieving revision 1.8.2.19
diff -u -r1.8.2.18 -r1.8.2.19
--- readme 2001/05/07 13:34:32 1.8.2.18
+++ readme 2001/05/08 01:31:19 1.8.2.19
@@ -1,4 +1,4 @@
-$Id: readme,v 1.8.2.18 2001/05/07 13:34:32 marcsaeg Exp $
+$Id: readme,v 1.8.2.19 2001/05/08 01:31:19 marcsaeg Exp $
Release Notes for:
====================
@@ -70,9 +70,14 @@
version 3.1 also focused on reorganizing the code (modularization, cleanup,
refactoring, removal of dead code, and separation of J2EE-specific code).
-- Tomcat 3.2 is the first performance tune-up, and also adds a few new
-features (see next section).
+- Tomcat 3.2 was the first performance tune-up, and also added a few new
+features.
+- Tomcat 3.2.1 was a security update. See section 7.3 for details.
+
+- Tomcat 3.2.2 is a bug fix release. Section 7.1 describes the issues
+that have been fixed in the version.
+
- Tomcat 4.0 is separate development from Tomcat 3.x. It is based on the
Catalina architecture, which is very different from the architecture of
Tomcat 3.x. In addition, Tomcat 4.0 is to be the reference implementation
@@ -281,6 +286,15 @@
javax.servlet.Context.getResrouceAsStream() cannot contain URL escapes of
the form %HH. Paths containing any URL escapes will return null.
+6.11 AJP12 and SSL
+
+The AJP12 protocol does not provide a mechanism for identifying requests
+that arrived on a secure transport (e.g. SSL). Tomcat assumes that any
+request that arrived on server port 443 is secure and sets the URL scheme
+to HTTPS. Requests on any other port are assumed to be non-secure and
+will indicate a URL scheme of HTTP. The AJP13 protocol does not suffer
+from this problem.
+
===============================================================================
7. FIXES AND ENHANCEMENTS IN UPDATES
@@ -318,6 +332,8 @@
- HttpServletRequest.encodeURL() now properly encodes URLs that contain
an anchor but no query string. (#1182)
- Error pages now work in virtual hosts.
+ - ServletRequest.getRemoteHost() now returns the remote IP address
+ if the remote host name isn't known. (#208)
Jasper
- Fix for UnsupportedEncodingException due to UTF8 instead of UTF-8. (#269)
