tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From craig...@apache.org
Subject cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.0-B7.txt
Date Fri, 10 Aug 2001 05:01:35 GMT
craigmcc    01/08/09 22:01:35

  Modified:    .        RELEASE-NOTES-4.0-B7.txt
  Log:
  Update release notes to reflect the current status of testing mod_webapp.
  
  Revision  Changes    Path
  1.3       +53 -10    jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B7.txt
  
  Index: RELEASE-NOTES-4.0-B7.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B7.txt,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- RELEASE-NOTES-4.0-B7.txt	2001/08/10 00:08:19	1.2
  +++ RELEASE-NOTES-4.0-B7.txt	2001/08/10 05:01:34	1.3
  @@ -3,7 +3,7 @@
                               Release Notes
                               =============
   
  -$Id: RELEASE-NOTES-4.0-B7.txt,v 1.2 2001/08/10 00:08:19 craigmcc Exp $
  +$Id: RELEASE-NOTES-4.0-B7.txt,v 1.3 2001/08/10 05:01:34 craigmcc Exp $
   
   
   ============
  @@ -21,7 +21,12 @@
   
   Please report bugs and feature requests under product name "Tomcat 4".
   
  +This version of Tomcat 4 should be considered a "release candidate" for
  +all capabilities except the mod_webapp connector.  Only bugfix changes will
  +be implemented before a Tomcat 4.0 final release is made available, which
  +will occur when the Servlet 2.3 and JSP 1.2 specifications go final.
   
  +
   ----> SECURITY VULNERABILITY FIXED:  In addition to the new features and
   ----> bug fixes listed below, this release of Tomcat fixes a vulnerability
   ----> on Windows 9x platforms (at least, possibly on other Windows versions
  @@ -30,7 +35,7 @@
   ----> Unix platforms.
   
   
  -----> UPCOMING CHANGE NOTICE:  In a future beta release of Tomcat 4.0, it
  +----> UPCOMING CHANGE NOTICE:  In a future release of Tomcat 4.0, it
   ----> is likely that the default operational mode will be to run Tomcat
   ----> under a security manager (rather than the current default of not
   ----> using one).  This may necessitate editing the policy permissions
  @@ -55,10 +60,10 @@
   Documentation - Revised the installation instructions, as well as instructions
   for building from source, to reflect current dependencies.
   
  -Spec Compliance - Tomcat 4 is now compliant with the changes in the Servlet 2.3
  -(Proposed Final Draft 3) and JSP 1.2 (Proposed Final Draft 3) specifications.
  -Further changes in the specifications are possible, but grow increasingly
  -unlikely as they approach final release.
  +Spec Compliance - Tomcat 4.0 is now compliant with the changes in the Servlet
  +2.3 (Proposed Final Draft 3) and JSP 1.2 (Proposed Final Draft 3)
  +specifications.  Further changes in the specifications are possible, but grow
  +increasingly unlikely as they approach final release.
   
   Documentation - Started migrating to a new "tomcat-docs" web app that uses a
   standard stylesheet to manage the creation of documentation (in HTML format).
  @@ -189,10 +194,9 @@
   walk up the directory tree and expose files, just like "../../.." type paths
   would if they were not normalized.
   
  -WARP Connector - Brought the sources of the WARP connector (used to talk with
  -Apache+mod_webapp) up to date with the most recent bugfixes.  Now passes all
  -Watchdog and tester tests when running Apache+Tomcat (as well as when running
  -Tomcat stand alone).
  +WarpConnector - Brought the sources of the WARP connector (used to talk with
  +Apache+mod_webapp) up to date with the most recent bugfixes.  See below for
  +current information about this connector.
   
   
   ----------------
  @@ -275,3 +279,42 @@
   errors when trying to use a different XML parser in a web application.
   
   
  +---------------------
  +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:
  +
  +    WebAppMount 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.  When Tomcat 4.0 final is released,
  +  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.
  +
  +* If you restart Tomcat, you must also restart Apache to avoid receiving
  +  "Error 400 - Bad Request" errors.  This will be handled transparently
  +  in the final release.
  +
  +* The combination of Apache+Tomcat currently passes all spec validation
  +  tests in the "jakarta-watchdog-4.0" suite.
  +
  +* There are several test failures in the "tester" unit test suite that will
  +  be corrected before final release.  (Most of these issues related to the
  +  bug that prevents BASIC authentication form operating.)
  
  
  

Mime
View raw message