remm 02/02/28 16:36:05
Modified: . Tag: tomcat_40_branch OUTSTANDING-BUGS-4.0.3.txt
RELEASE-NOTES-4.0.3-B1.txt
Log:
- Update bug status.
- Remove a few obsolete release notes.
Revision Changes Path
No revision
No revision
1.1.2.9 +6 -2 jakarta-tomcat-4.0/Attic/OUTSTANDING-BUGS-4.0.3.txt
Index: OUTSTANDING-BUGS-4.0.3.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/Attic/OUTSTANDING-BUGS-4.0.3.txt,v
retrieving revision 1.1.2.8
retrieving revision 1.1.2.9
diff -u -r1.1.2.8 -r1.1.2.9
--- OUTSTANDING-BUGS-4.0.3.txt 28 Feb 2002 01:04:51 -0000 1.1.2.8
+++ OUTSTANDING-BUGS-4.0.3.txt 1 Mar 2002 00:36:05 -0000 1.1.2.9
@@ -7,15 +7,19 @@
acceptable to delay their resolution.
+4964 jasper popBody() is called before doEndTag() is called in a BodyTag
5507 catalina Swapping sessions causes exceptions and it doesn't work
with FileStore
+5741 jasper Jspc -webapp option is broken due to namespace collisions
5827 catalina DataInputStream.readInt returns wrong values
-5976 catalina Tomcat 4.0.2B2 + Security Manager + JSSE don't work together
+5853 catalina Unable to get request parameters in the Error page
+ for form based login
+5998 jasper Exception hiding when a JspExceptioin is thrown by a tag
6068 jk AJP13 "bad read", IOException
+6281 catalina JDBCRealm+Form Login+URL re-writing session=broken
6331 jk Cannot add more than one cookie
6420 jk Loadbalancer mod_jk from 4.02 not working with TC 3.3
6457 jk mod_jk causes segmentation fault with JkLogLevel != debug
-6464 jasper Jspc generates bad package names on Windows NT
6617 catalina Iterating over session attribute name enumeration fails
1.1.2.14 +4 -37 jakarta-tomcat-4.0/Attic/RELEASE-NOTES-4.0.3-B1.txt
Index: RELEASE-NOTES-4.0.3-B1.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/Attic/RELEASE-NOTES-4.0.3-B1.txt,v
retrieving revision 1.1.2.13
retrieving revision 1.1.2.14
diff -u -r1.1.2.13 -r1.1.2.14
--- RELEASE-NOTES-4.0.3-B1.txt 28 Feb 2002 00:35:04 -0000 1.1.2.13
+++ RELEASE-NOTES-4.0.3-B1.txt 1 Mar 2002 00:36:05 -0000 1.1.2.14
@@ -3,7 +3,7 @@
Release Notes
=============
-$Id: RELEASE-NOTES-4.0.3-B1.txt,v 1.1.2.13 2002/02/28 00:35:04 remm Exp $
+$Id: RELEASE-NOTES-4.0.3-B1.txt,v 1.1.2.14 2002/03/01 00:36:05 remm Exp $
============
@@ -144,13 +144,15 @@
correctly
6641 Download of MS Office docs from protected areas fail with IE
6644 Whitespace after Content-type header value leads to POST method failure
+6668 HttpProcessor takes incorrect defaults for proxy port according
+ to HTTP/1.1 Spec
+6772 [Security] RequestDipatcher allows to bypass security manager sandboxing
============================
KNOWN ISSUES IN THIS RELEASE:
============================
-* Tomcat 4.0 and Apache
* Tomcat 4.0 and JNI Based Applications
* Tomcat 4.0 Standard APIs Available
* Tomcat 4.0 and XML Parsers
@@ -161,41 +163,6 @@
* Tomcat 4.0 and Apache Cocoon 2.0
* Enabling SSI and CGI Support
* Tomcat 4.0 and Sun JDK 1.4 beta 3
-
-
----------------------
-Tomcat 4.0 and Apache:
----------------------
-
-The binary distribution for Tomcat 4.0 includes the most recent stable version
-of the WARP connector, which is the Tomcat component that talks to mod_webapp
-inside Apache 1.3. The current state of this support is summarized as follows:
-
-* The mod_webapp connector is configured based on the contents of the
- web.xml file for your web application. The only required per-webapp
- configuration information in your Apache 1.3 httpd.conf file is
- something like this:
-
- WebAppDeploy examples warpConnection /examples/
-
- which causes mod_webapp to automatically recognize all of your servlet
- mappings, security constraints, and other configuration elements.
-
-* Currently, mod_webapp forwards *all* requests under the specified
- context path to Tomcat for processing. In a futher release,
- it will automatically configure itself to serve static resources
- from Apache *unless* the resource is subject to filtering, or subject
- to a security constraint, as defined in web.xml. No extra configuration
- in httpd.conf will be required.
-
-* With this release, FORM-based authentication will work correctly, but
- there is a bug that prevents BASIC authentication from operating. This
- will be addressed before final release.
-
-* The combination of Apache+Tomcat currently passes all spec validation
- tests in the "jakarta-watchdog-4.0" suite.
-
-The WARP connector for Tomcat 4.0 does not support load balancing at this time.
-------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
