DO NOT REPLY [Bug 6360] - request.getSession(true) may return null
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6360. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6360 request.getSession(true) may return null --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 08:21 --- Excerpt from the Servlet 2.2 spec: Using a Request Dispatcher To use a request dispatcher, a developer needs to call either the include or forward method of the RequestDispatcher interface using the request and response arguments that were passed in via the service method of the Servlet interface. The Container Provider must ensure that the dispatch to a target servlet occurs in the same thread of the same VM as the original request. - current Tomcat 3.3 implementation seems to forward the request in a new thread, which causes additional problems (that's why I needed to use include for my workaround, which is quite different with new side-effects - but runs in the same thread) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6419] - Catalina does not stop
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6419. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6419 Catalina does not stop [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 08:40 --- The logs indicate that all webapps and Catalina components have been properly shut down (connectors + all webapps). All of the remaining Tomcat threads should be daemon threads, so the VM should exit. If it doesn't, then it means there are still some non-daemon threads running, but they were not started by Tomcat itself. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6286] - Spaces should be allowed in Servlet Context paths
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6286. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6286 Spaces should be allowed in Servlet Context paths [EMAIL PROTECTED] changed: What|Removed |Added Severity|Major |Normal Status|NEW |RESOLVED Resolution||LATER --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 08:50 --- Spaces are not allowed in context paths, and probably won't be for some time. Spaces are allowed in many other paths, OTOH. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6388] - Duplicate files in jakarta-tomcat-4.0.2.tar.gz
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6388. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6388 Duplicate files in jakarta-tomcat-4.0.2.tar.gz [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 08:58 --- This has been fixed. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 OUTSTANDING-BUGS-4.0.3.txt
remm02/02/14 01:12:08 Modified:.Tag: tomcat_40_branch OUTSTANDING-BUGS-4.0.3.txt Log: - Update bug list. Revision ChangesPath No revision No revision 1.1.2.3 +20 -9 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.2 retrieving revision 1.1.2.3 diff -u -r1.1.2.2 -r1.1.2.3 --- OUTSTANDING-BUGS-4.0.3.txt13 Feb 2002 01:50:46 - 1.1.2.2 +++ OUTSTANDING-BUGS-4.0.3.txt14 Feb 2002 09:12:08 - 1.1.2.3 @@ -2,27 +2,38 @@ Tomcat 4.0.3 Final bug status - -This document lists bug that should be addressed before 4.0.2 Final is +This document lists bug that should be addressed before 4.0.3 Final is released. None of these bugs are regression problems, so it should be acceptable to delay their resolution. +3509webapp Apache 1.3.20 mod_webapp Tomcat 4b7 HANGS under Win +4518jasper load-on-startup is not working with jsp page 4793webapp mod_webapp connector doesn´t work 4930webapp java.io.StreamCorruptedException: Type code out of range, is 0 with Apache WebApp module 5040webaap EOFException when talking from applet to servlet via mod_webapp -5402webapp WarpConnection raise IOException +5402webapp WarpConnection raise IOException in a Clustered + Solaris environment +5704servlets CgiServlet corrupting images? 5735catalina HTTP connector running out of processors under heavy load +5759servlets CGI servlet mapping by extension *.cgi does not work 5795catalina Catalina Shutdown relies on localhost causing problems - in a Clustered Solaris environment 5827catalina DataInputStream.readInt returns wrong values 5899servlets HTTP POST parameters ignored in CGIServlet.java +5976catalina Spaces should be allowed in Servlet Context paths 6036webapp Problems with URI mapping -3509webapp Apache 1.3.20 mod_webapp Tomcat 4b7 HANGS under Win -5704servlets CgiServlet corrupting images? -4518jasper load-on-startup is not working with jsp page -5759servlets CGI servlet mapping by extension *.cgi does not work -6400jasper Tag Libraries not deploying in 4.0.2 final - +6068jk AJP13 bad read, IOException +6219jk FORM authentication does not work when using AJP connector +6331catalina Cannot add more than one cookie +6376jasper Improper import statement is generated when JSP page + extends a custom class without package prefix +6411catalina HttpSession.isNew() always returns false +6420jk Loadbalancer mod_jk from 4.02 not working with TC 3.3 +6432jasper Jasper should validate that an XML-view of a JSP page + conforms as much as possible based on the DTD supplied + in JSP.B of the JSP 1.2 specification +6443jasper Jasper doesn't follow the spec in regards to the xml-view + of a JSP page and whitespace handling semantics -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
FW: RES: [ANNOUCEMENT] Tomcat 4.0.2 Final released
Might be worth forwarding it to tomcat-dev (the guy sent to announcements) Pier -- Forwarded Message From: Edson Carlos Ericksson Richter [EMAIL PROTECTED] Date: Wed, 13 Feb 2002 16:05:43 -0300 To: Jakarta Announcements List [EMAIL PROTECTED] Subject: RES: [ANNOUCEMENT] Tomcat 4.0.2 Final released Are not the RELEASE-NOTES updated? See following secition of known problems: The WARP connector for Tomcat 4.0 does not support load balancing at this time. and The AJP connector for Tomcat 4.0 does not support load balancing at this time. Thanks, Edson Carlos Ericksson Richter Gerente de Tecnologia ECONET Soluções Web +55 61 326 5115 -Mensagem original- De: Remy Maucherat [mailto:[EMAIL PROTECTED]] Enviada em: segunda-feira, 11 de fevereiro de 2002 14:05 Para: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Assunto: [ANNOUCEMENT] Tomcat 4.0.2 Final released The Tomcat Team is proud to announce the final release of Tomcat 4.0.2. Highlights in this release include: - Full support for the AJP 1.3 and 1.4 native connector protocols, including load balancing - Updated mod_webapp native connector - Performance improvements for single thread model servlets - And many bugfixes Downloads (source and binary): http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.2/ Note: RPMs and binaries of native connectors will be made available shortly. Release notes (including the full list of changes, bugfixes, as well as the known issues with this release): http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.2/RELEASE-N OTES Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- End of Forwarded Message -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6457] New: - mod_jk causes segmentation fault with JkLogLevel != debug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6457. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6457 mod_jk causes segmentation fault with JkLogLevel != debug Summary: mod_jk causes segmentation fault with JkLogLevel != debug Product: Tomcat 4 Version: 4.0.2 Final Platform: Sun OS/Version: Solaris Status: NEW Severity: Critical Priority: Other Component: JK/AJP Connector AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Platform: Solaris 8, Sparc Webserver: Apache 1.3.22 Servlet container: Tomcat 4.0.2 mod_jk was built using the build-solaris.sh script. When using mod_jk/1.1.0 (from jakarta-tomcat-3.3a) things work just fine. But when we use mod_jk/1.2.0 (from jakarta-tomcat-connectors-4.0.2-src) we get the entires in Apaches error_log that look like this, when we try to access a servlet or jsp: [Thu Feb 14 10:58:30 2002] [notice] child pid 13024 exit signal Segmentation Fault (11) When we change JkLogLevel to debug from info things start to work. All loglevels beside debug causes segmentation faults. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6460] New: - Problem of very long response time for servlet which don't return any response.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6460. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6460 Problem of very long response time for servlet which don't return any response. Summary: Problem of very long response time for servlet which don't return any response. Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Using a DummyServlet which logs a request for example. This servlet doesn't need to return anything to the client machine (no HTML, XML or whatever bytes array ). Using Tomcat 4.01 this kind of servlet has very large response times (I guess that Catalina wait for any timeout before closing the stream). Adding a dummy: PrintWriter writer = response.getWriter(); writer.close(); (the same trick works with the getOutputStream() method of course). is a workaround for this problem... This problem occured with the new catalina architecture because my code was working properly with the Tomcat 3.2.3 release. The problem induces an application response time increased by a *50 factor... The bug doesn't seem to depend on the client VM because it was reproduced running 1.3.1 Sun VM on Linux Win2K machines. The Tomcat 4.01 release used is the one found in the JBoss-Tomcat bundle, as I previously used the Tomcat 3.2.3 coupled with Jboss 2.4.4. The bug occurs only with this kind of servlet because the rest of my application uses XML for transmitting values to clients there 's no overhead (not viewable without profiler tool...). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6462] New: - request.getRemoteAddr() returns 127.0.0.1
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6462. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6462 request.getRemoteAddr() returns 127.0.0.1 Summary: request.getRemoteAddr() returns 127.0.0.1 Product: Tomcat 3 Version: 3.3 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Servlet AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Using 3.3 the request.getRemoteAddr() method seems to return 127.0.0.1 after the first two requests. This happens with 3.3a too. You can try with the sample servlet /examples/servlet/RequestInfoExample using a single client or different clients. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/xdocs news.xml
larryi 02/02/14 05:34:25 Modified:xdocsnews.xml Log: Update for Tomcat 3.3.1 Beta 1 release Revision ChangesPath 1.15 +15 -0 jakarta-tomcat-site/xdocs/news.xml Index: news.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs/news.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- news.xml 11 Feb 2002 08:45:51 - 1.14 +++ news.xml 14 Feb 2002 13:34:25 - 1.15 @@ -10,6 +10,21 @@ section name=News amp; Status +h314 February 2002 - Jakarta Tomcat 3.3.1 Beta 1 Released/h3 + +pTomcat 3.3.1 Beta 1 is the first beta release of Tomcat 3.3.1. +This release contains numerous bug fixes and small feature additions +to Tomcat 3.3(a). You can find everything, including a list of the +changes, +a href=http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3.1-b1/;here/a./p + +pThe online a href=http://jakarta.apache.org/tomcat/tomcat-3.3-doc/index.html; +Tomcat 3.3 Documentation/a includes information on this release. +New features are noted as specific to Tomcat 3.3.1. For the most up to +date Tomcat 3.3 documentation, please refer to this site./p + +hr noshade=noshade size=1/ + h311 February 2002 - Tomcat 4.0.2 Final Released/h3 pThis is the final release of Tomcat 4.0.2, which is a maintenance release of Tomcat 4.0. Download it -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/docs news.html
larryi 02/02/14 05:34:33 Modified:docs news.html Log: Update for Tomcat 3.3.1 Beta 1 release Revision ChangesPath 1.17 +12 -1 jakarta-tomcat-site/docs/news.html Index: news.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/news.html,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- news.html 11 Feb 2002 08:45:51 - 1.16 +++ news.html 14 Feb 2002 13:34:33 - 1.17 @@ -109,7 +109,18 @@ /td/tr trtd blockquote -h311 February 2002 - Tomcat 4.0.2 Final Released/h3 +h314 February 2002 - Jakarta Tomcat 3.3.1 Beta 1 Released/h3 +pTomcat 3.3.1 Beta 1 is the first beta release of Tomcat 3.3.1. +This release contains numerous bug fixes and small feature additions +to Tomcat 3.3(a). You can find everything, including a list of the +changes, +a href=http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3.1-b1/;here/a./p +pThe online a href=http://jakarta.apache.org/tomcat/tomcat-3.3-doc/index.html; +Tomcat 3.3 Documentation/a includes information on this release. +New features are noted as specific to Tomcat 3.3.1. For the most up to +date Tomcat 3.3 documentation, please refer to this site./p +hr noshade=noshade size=1 / +h311 February 2002 - Tomcat 4.0.2 Final Released/h3 pThis is the final release of Tomcat 4.0.2, which is a maintenance release of Tomcat 4.0. Download it a href=http://www.apache.org/dist/jakarta/jakarta-tomcat-4.0/release/v4.0.2/;here/a./p -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/webpages index.html
larryi 02/02/14 06:23:28 Modified:src/webpages index.html Log: Revert to dev status Revision ChangesPath 1.23 +2 -2 jakarta-tomcat/src/webpages/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat/src/webpages/index.html,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- index.html8 Feb 2002 13:15:22 - 1.22 +++ index.html14 Feb 2002 14:23:28 - 1.23 @@ -4,13 +4,13 @@ meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 meta name=GENERATOR content=Mozilla/4.72 [en] (WinNT; U) [Netscape] meta name=Author content=Anil K. Vijendran -titleTomcat v3.3.1 Beta 1/title +titleTomcat v3.3.1 Dev/title /head body bgcolor=#FF img SRC=tomcat.gif height=92 width=130 align=LEFTbfont face=Arial, Helvetica, sans-seriffont size=+3Tomcat/font/font/b br bfont face=Arial, Helvetica, sans-seriffont size=-1Version -3.3.1 Beta 1/font/font/b +3.3.1 Dev/font/font/b pThis is the default Tomcat home page. This page serves as a quick reference guide to related resources and is located at: ul -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core ContextManager.java
larryi 02/02/14 06:23:44
Modified:src/share/org/apache/tomcat/core ContextManager.java
Log:
Revert to dev status
Revision ChangesPath
1.201 +1 -1
jakarta-tomcat/src/share/org/apache/tomcat/core/ContextManager.java
Index: ContextManager.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/core/ContextManager.java,v
retrieving revision 1.200
retrieving revision 1.201
diff -u -r1.200 -r1.201
--- ContextManager.java 8 Feb 2002 13:13:32 - 1.200
+++ ContextManager.java 14 Feb 2002 14:23:43 - 1.201
@@ -148,7 +148,7 @@
public class ContextManager {
/** Official name and version
*/
-public static final String TOMCAT_VERSION = 3.3.1 Beta 1;
+public static final String TOMCAT_VERSION = 3.3.1 Dev;
public static final String TOMCAT_NAME = Tomcat Web Server;
/** System property used to set the base directory ( tomcat home ).
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/doc readme-3.3.1 index.html readme
larryi 02/02/14 06:25:53 Modified:src/doc index.html readme Added: src/doc readme-3.3.1 Log: Keep readme file a 3.3 document. Add a readme-3.3.1 to cover changes since 3.3. Update index.html to reference both. Revision ChangesPath 1.10 +3 -4 jakarta-tomcat/src/doc/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat/src/doc/index.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- index.html28 Nov 2001 11:15:06 - 1.9 +++ index.html14 Feb 2002 14:25:53 - 1.10 @@ -1,7 +1,7 @@ html head -!-- $Id: index.html,v 1.9 2001/11/28 11:15:06 larryi Exp $ -- +!-- $Id: index.html,v 1.10 2002/02/14 14:25:53 larryi Exp $ -- !-- Copyright 1999, Apache Software Foundation -- meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 link rel=stylesheet href=style.css @@ -29,9 +29,8 @@ h1Tomcat Documentation/h1 ul -li a href=readmeTomcat 3.3 Release Notes/abr - nbsp; -/li +li a href=readmeTomcat 3.3 Release Notes/a/li +li a href=readme-3.3.1Tomcat 3.3.1 Release Notes/abrnbsp;/li li Using Tomcat ul 1.24 +4 -4 jakarta-tomcat/src/doc/readme Index: readme === RCS file: /home/cvs/jakarta-tomcat/src/doc/readme,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- readme8 Feb 2002 13:14:13 - 1.23 +++ readme14 Feb 2002 14:25:53 - 1.24 @@ -1,9 +1,9 @@ -$Id: readme,v 1.23 2002/02/08 13:14:13 larryi Exp $ +$Id: readme,v 1.24 2002/02/14 14:25:53 larryi Exp $ Release Notes for: - == - TOMCAT Version 3.3.1 Beta1 - == + = + Apache Tomcat Version 3.3 + = 0. TABLE OF CONTENTS: 1.1 jakarta-tomcat/src/doc/readme-3.3.1 Index: readme-3.3.1 === $Id: readme-3.3.1,v 1.1 2002/02/14 14:25:53 larryi Exp $ Release Notes for: === Apache Tomcat Version 3.3.1 === This document describes the changes that have been made since the last release of Tomcat 3.3. = Bug Fixes = Feature Additions: Bug No. Description Restored prefix attribute to InvokerInterceptor. It was available in Tomcat 3.2.x. Added SingleThreadModel pooling to ServletHandler. The default is to use pooling. Added optional checking (configured on SessionId module) to ensure that the SSL session IDs match for each request within a Tomcat session. This check is disabled by default. Added org.apache.tomcat.util.net.URL class from Tomcat 4.0 so response.encodeURL() can work under SSL without JSSE. This can occur if you have Apache forwarding SSL requests to a Tomcat that doesn't have JSSE installed. Fixed logic for response.encodeURL() so that it will work correctly if the input URL includes an anchor tag. Improved the handling of invalid web.xml files. Now you get the same error messages every time you parse the file. Moved the setting of the default *.jsp mapping so that it is now possible to entirely disable support for jsp files. Fixed problem with jsp_precompile parameter to JSP files. Context properties and ContextManager properties can now be set with Property ... / elements, i.e: Property name=propname value=thevalue / For backwards compatibility, the ContextManager lower-case-p property ... / version supported by Tomcat 3.3. is still supported. Added variable substitution handling to ContextXmlReader, allowing variable substitution to be used in Context .../Context declarations. Added support for PureTLS as an SSL option. Also, any attribute used to create the socket factory, such as rootfile (or keystoreType for JSSE), is now settable on the Http10Connector element in server.xml. The configuration files generated by ApacheConfig, IISConfig and NSConfig were improved for the case when the forwardAll attribute is false.
DO NOT REPLY [Bug 6464] New: - jspc generates bad package names on Windows NT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6464. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6464 jspc generates bad package names on Windows NT Summary: jspc generates bad package names on Windows NT Product: Tomcat 4 Version: 4.0.2 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] How to reproduce : -- Find a computer running Windows NT. Directory structure : x\en\demo.jsp cd x jspc -uriroot . -d . en/demo.jsp file generated : x\demo.java package name in source : none jspc -p en en/demo.jsp file generated : x\demo.java package name in source : package en.; Both commands should have generated x\en\demo.java, with a package name of en. More info : --- The reason seems to be the incorrect use of '/' as a path separator in org.apache.jasper.CommandLineContext.getServletPackageName() Replacing '/' with '\\' solved the proble on NT. But then, it would not work on Unix. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6462] - request.getRemoteAddr() returns 127.0.0.1
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6462. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6462 request.getRemoteAddr() returns 127.0.0.1 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 14:51 --- The mentioned fix appears in the Tomcat 3.3.1 Beta 1 release. *** This bug has been marked as a duplicate of 4564 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4564] - request.getRemoteAddr() and AccesLog not working
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4564. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4564 request.getRemoteAddr() and AccesLog not working [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 14:51 --- *** Bug 6462 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RES: [ANNOUCEMENT] Tomcat 4.0.2 Final released
Might be worth forwarding it to tomcat-dev (the guy sent to announcements) Yep ;) Are not the RELEASE-NOTES updated? See following secition of known problems: The WARP connector for Tomcat 4.0 does not support load balancing at this time. and The AJP connector for Tomcat 4.0 does not support load balancing at this time. The AJP connector support mod_jk LOAD-BALANCING since 4.0.2 :) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeansMBeanUtils.java mbeans-descriptors.xml
On Thu, 14 Feb 2002, Remy Maucherat wrote:
Date: Thu, 14 Feb 2002 00:01:06 -0800
From: Remy Maucherat [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: Re: cvs commit:
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java mbeans-descriptors.xml
amyroh 02/02/13 23:47:14
Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java mbeans-descriptors.xml
Log:
Add additional Catalina components MBeans.
if (managed == null) {
-//Exception e = new Exception(ManagedBean is not found
with +mname);
-//throw new MBeanException(e);
-return null;
+Exception e = new Exception(ManagedBean is not found with
+mname);
+throw new MBeanException(e);
As I said before, I think it's a very bad idea to do this, and would
restrict the audience of the admin webapp to the beginner users of Tomcat
(since you get the choice between using the webapp *or* taking advantage of
the modularity of Catalina).
At the moment, the other alternative (just skip the components you don't
know how to create an MBean for) is even worse:
* Tomcat starts up, the custom components are created,
but no MBeans for the custom components
* Admin app shows only the known components, thus mystifying the user
* User makes a change, via the admin app, to a standard component
* (When supported) Admin app rewrites server.xml to save the change
* The unrecognized custom entry disappears from server.xml :-(.
There will certainly need to be a way to deal with extensibility (i.e.
user defined Valves, Realms, and so on). But we need to start from the
assumption that the admin app must faithfully reproduce *all* of the
contents of the server.xml file when it supports persistence. Silently
ignoring things you don't know about doesn't help achieve that goal.
Remy
Craig
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6468] New: - content-type not set for errors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6468. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6468 content-type not set for errors Summary: content-type not set for errors Product: Tomcat 4 Version: 4.0.2 Final Platform: PC URL: http://localhost:8080/nocontext/ OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: HTTP/1.1 Connector AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] tomcat 4.0.1 sets the Content-type: http header for its error messages. tomcat 4.0.2 does not set the header at all, which causes my mozilla to disply the source, instead of the rendered page. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector ResponseBase.java
remm02/02/14 09:03:26
Modified:catalina/src/share/org/apache/catalina/connector Tag:
tomcat_40_branch ResponseBase.java
Log:
- Don't commit when using getReporter.
- Fix bug 6468.
Revision ChangesPath
No revision
No revision
1.16.2.2 +4 -9
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java
Index: ResponseBase.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java,v
retrieving revision 1.16.2.1
retrieving revision 1.16.2.2
diff -u -r1.16.2.1 -r1.16.2.2
--- ResponseBase.java 4 Oct 2001 19:26:57 - 1.16.2.1
+++ ResponseBase.java 14 Feb 2002 17:03:26 - 1.16.2.2
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java,v
1.16.2.1 2001/10/04 19:26:57 remm Exp $
- * $Revision: 1.16.2.1 $
- * $Date: 2001/10/04 19:26:57 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java,v
1.16.2.2 2002/02/14 17:03:26 remm Exp $
+ * $Revision: 1.16.2.2 $
+ * $Date: 2002/02/14 17:03:26 $
*
*
*
@@ -89,7 +89,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.16.2.1 $ $Date: 2001/10/04 19:26:57 $
+ * @version $Revision: 1.16.2.2 $ $Date: 2002/02/14 17:03:26 $
*/
public abstract class ResponseBase
@@ -520,11 +520,6 @@
if (isError()) {
-try {
-flushBuffer();
-} catch (IOException e) {
-;
-}
try {
if (this.stream == null)
this.stream = createOutputStream();
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector ResponseBase.java
remm02/02/14 09:03:39
Modified:catalina/src/share/org/apache/catalina/connector
ResponseBase.java
Log:
- Don't commit when using getReporter.
- Fix bug 6468.
Revision ChangesPath
1.20 +4 -9
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java
Index: ResponseBase.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- ResponseBase.java 28 Sep 2001 23:34:02 - 1.19
+++ ResponseBase.java 14 Feb 2002 17:03:39 - 1.20
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java,v
1.19 2001/09/28 23:34:02 remm Exp $
- * $Revision: 1.19 $
- * $Date: 2001/09/28 23:34:02 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/ResponseBase.java,v
1.20 2002/02/14 17:03:39 remm Exp $
+ * $Revision: 1.20 $
+ * $Date: 2002/02/14 17:03:39 $
*
*
*
@@ -89,7 +89,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.19 $ $Date: 2001/09/28 23:34:02 $
+ * @version $Revision: 1.20 $ $Date: 2002/02/14 17:03:39 $
*/
public abstract class ResponseBase
@@ -520,11 +520,6 @@
if (isError()) {
-try {
-flushBuffer();
-} catch (IOException e) {
-;
-}
try {
if (this.stream == null)
this.stream = createOutputStream();
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6468] - content-type not set for errors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6468. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6468 content-type not set for errors [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 17:07 --- Mozilla 0.9.8 still displays the error page (at least on Windows). The problem is now fixed in both branches (4.0 and HEAD). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat 3.3.1 Beta 1 Released
RPMs are also available : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1-b1/rpms/ Take a look at the information on how to use PureTLS, the OSS alternative to JSSE, which use Cryptix as security provider. May be updated in Tomcat Doc also, BTW: What about PureTLS on jakarta ? Could we host these CRYPTO rpms at apache.org since they give users a 100% OSS SSL implementation for TC 3.3 now and may be soon TC 4.0 ? PureTLS and Cryptix are both BSD so licence is not a problem. If it's impossible to host these files on apache.org, could cryptix.org and rtfm.com hosts them ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6460] - Problem of very long response time for servlet which don't return any response.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6460. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6460 Problem of very long response time for servlet which don't return any response. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 17:29 --- Tomcat appears to be generating a correct answer when using a VoidServlet (with an empty service method), so it may be an issue with the HTTP client you're using. If you think it's not, I will need a test servlet to go further. Note: If there's a problem with the current HTTP/1.1 connector, you can use the HTTP/1.0 connector instead. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 OUTSTANDING-BUGS-4.0.3.txt RELEASE-NOTES-4.0.3-B1.txt
remm02/02/14 09:32:25 Modified:.Tag: tomcat_40_branch OUTSTANDING-BUGS-4.0.3.txt RELEASE-NOTES-4.0.3-B1.txt Log: - Update release notes (remove outdated note on AJP). - Update bug status. Revision ChangesPath No revision No revision 1.1.2.4 +3 -0 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.3 retrieving revision 1.1.2.4 diff -u -r1.1.2.3 -r1.1.2.4 --- OUTSTANDING-BUGS-4.0.3.txt14 Feb 2002 09:12:08 - 1.1.2.3 +++ OUTSTANDING-BUGS-4.0.3.txt14 Feb 2002 17:32:25 - 1.1.2.4 @@ -36,4 +36,7 @@ in JSP.B of the JSP 1.2 specification 6443jasper Jasper doesn't follow the spec in regards to the xml-view of a JSP page and whitespace handling semantics +6464jasper Jspc generates bad package names on Windows NT + + 1.1.2.3 +2 -20 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.2 retrieving revision 1.1.2.3 diff -u -r1.1.2.2 -r1.1.2.3 --- RELEASE-NOTES-4.0.3-B1.txt14 Feb 2002 02:27:23 - 1.1.2.2 +++ RELEASE-NOTES-4.0.3-B1.txt14 Feb 2002 17:32:25 - 1.1.2.3 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-4.0.3-B1.txt,v 1.1.2.2 2002/02/14 02:27:23 remm Exp $ +$Id: RELEASE-NOTES-4.0.3-B1.txt,v 1.1.2.3 2002/02/14 17:32:25 remm Exp $ @@ -98,6 +98,7 @@ when the Oracle 8.1.7 JDBC driver classes are added to this shared class loader directory 6400 Tag Libraries not deploying in 4.0.2 final +6468 Content-type not set for errors @@ -105,7 +106,6 @@ * Tomcat 4.0 and Apache -* Tomcat 4.0 and AJP 1.3 * Tomcat 4.0 and JNI Based Applications * Tomcat 4.0 Standard APIs Available * Tomcat 4.0 and XML Parsers @@ -151,24 +151,6 @@ tests in the jakarta-watchdog-4.0 suite. The WARP connector for Tomcat 4.0 does not support load balancing at this time. - --- -Tomcat 4.0 and AJP 1.3: --- - -Tomcat 4.0 now includes support for the AJP 1.3 protocol, which the -mod_jk collection of native webserver modules implements. - -The AJP connector is not enabled by default. To enable it, uncomment -the following section in $CATALINA_HOME/conf/server.xml: - -!-- -Connector className=org.apache.ajp.tomcat4.Ajp13Connector - port=8009 minProcessors=5 maxProcessors=75 - acceptCount=10 debug=0/ --- - -The AJP 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]
Re: RES: [ANNOUCEMENT] Tomcat 4.0.2 Final released
Are not the RELEASE-NOTES updated? See following secition of known problems: The WARP connector for Tomcat 4.0 does not support load balancing at this time. and The AJP connector for Tomcat 4.0 does not support load balancing at this time. I've removed the conflicting statement in the release notes (and updated the release notes in CVS for the next release). Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans MBeanUtils.java mbeans-descriptors.xml
amyroh 02/02/13 23:47:14
Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java mbeans-descriptors.xml
Log:
Add additional Catalina components MBeans.
if (managed == null) {
-//Exception e = new Exception(ManagedBean is not found
with +mname);
-//throw new MBeanException(e);
-return null;
+Exception e = new Exception(ManagedBean is not found
with
+mname);
+throw new MBeanException(e);
As I said before, I think it's a very bad idea to do this, and would
restrict the audience of the admin webapp to the beginner users of
Tomcat
(since you get the choice between using the webapp *or* taking advantage
of
the modularity of Catalina).
At the moment, the other alternative (just skip the components you don't
know how to create an MBean for) is even worse:
* Tomcat starts up, the custom components are created,
but no MBeans for the custom components
* Admin app shows only the known components, thus mystifying the user
* User makes a change, via the admin app, to a standard component
* (When supported) Admin app rewrites server.xml to save the change
* The unrecognized custom entry disappears from server.xml :-(.
There will certainly need to be a way to deal with extensibility (i.e.
user defined Valves, Realms, and so on). But we need to start from the
assumption that the admin app must faithfully reproduce *all* of the
contents of the server.xml file when it supports persistence. Silently
ignoring things you don't know about doesn't help achieve that goal.
I agree that it makes the task more complex, but I think that choice makes
the admin webapp a fancy feature, rather than a truly useful feature.
For example, if you write somthing as simple as a custom realm (or extend
one of the base ones) and add it to your server.xml, the admin webapp won't
work anymore (and you'll get some nasty stack trace printed out on your
command line when you start Catalina).
IMO, the pluggability feature should be developped first, rather than later.
Remy
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5330] - JNDI ENC context problem.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5330. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5330 JNDI ENC context problem. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 18:45 --- The fix is included in 4.0.2. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6360] - request.getSession(true) may return null
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6360. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6360 request.getSession(true) may return null [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 19:37 --- AFAIK the only way that request.getSession(true) can return null is if the number of active sessions exceeds maxActiveSessions. Also, rd.forward is executed in the same thread as the original request. This looks very much like a common programmer error when using frames. The browser will usually request the frames in parallel, so that each one ends up getting its own session. The fix is to do: frame src=%= response.encodeURL(/frame1.jsp) % ... Since I can't reproduce this, I'm marking it as invalid. Feel free to re-open with a test case that reproduces this. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6341] - tomcat dies on startup
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6341. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6341 tomcat dies on startup [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 19:40 --- I'm using JBindery to start tomcat, with the tomcat.home defined in the Properties panel (see http://www.rainwatersoft.com/java4u/tomcat_on_macintosh/ for instructions provided by Basil Bourqe). According to the JBindery docs, this is equivalent to using a -D flag, so that is not a potential fix. My os.name property is Mac OS, but even using that and .. is a bit of a hack, as it breaks the platform independence of java. Maybe you can accomplish something similar with File.getParent(). I'd send a patch, but I'm swamped here. If anyone fixes this, and would like me to test it on Mac OS X, that's no problem. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 3770] - HttpSessionListener.sessionCreated() called twice for each session
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3770. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3770 HttpSessionListener.sessionCreated() called twice for each session [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|LATER | --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 19:52 --- Reopen. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core StandardContext.java
remm02/02/14 11:54:01
Modified:catalina/src/share/org/apache/catalina/core Tag:
tomcat_40_branch StandardContext.java
Log:
- Prevent a listener from being added twice.
- Should fix bug 3770.
Revision ChangesPath
No revision
No revision
1.78.2.11 +9 -6
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java
Index: StandardContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
retrieving revision 1.78.2.10
retrieving revision 1.78.2.11
diff -u -r1.78.2.10 -r1.78.2.11
--- StandardContext.java 7 Jan 2002 19:07:24 - 1.78.2.10
+++ StandardContext.java 14 Feb 2002 19:54:00 - 1.78.2.11
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.78.2.10 2002/01/07 19:07:24 remm Exp $
- * $Revision: 1.78.2.10 $
- * $Date: 2002/01/07 19:07:24 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.78.2.11 2002/02/14 19:54:00 remm Exp $
+ * $Revision: 1.78.2.11 $
+ * $Date: 2002/02/14 19:54:00 $
*
*
*
@@ -142,7 +142,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.78.2.10 $ $Date: 2002/01/07 19:07:24 $
+ * @version $Revision: 1.78.2.11 $ $Date: 2002/02/14 19:54:00 $
*/
public class StandardContext
@@ -1208,9 +1208,12 @@
public void addApplicationListener(String listener) {
synchronized (applicationListeners) {
-String results[] =new String[applicationListeners.length + 1];
-for (int i = 0; i applicationListeners.length; i++)
+String results[] = new String[applicationListeners.length + 1];
+for (int i = 0; i applicationListeners.length; i++) {
+if (listener.equals(applicationListeners[i]))
+return;
results[i] = applicationListeners[i];
+}
results[applicationListeners.length] = listener;
applicationListeners = results;
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core StandardContext.java
remm02/02/14 11:54:12
Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
Log:
- Prevent a listener from being added twice.
- Should fix bug 3770.
Revision ChangesPath
1.95 +8 -5
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java
Index: StandardContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -r1.94 -r1.95
--- StandardContext.java 11 Feb 2002 22:21:58 - 1.94
+++ StandardContext.java 14 Feb 2002 19:54:12 - 1.95
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.94 2002/02/11 22:21:58 remm Exp $
- * $Revision: 1.94 $
- * $Date: 2002/02/11 22:21:58 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.95 2002/02/14 19:54:12 remm Exp $
+ * $Revision: 1.95 $
+ * $Date: 2002/02/14 19:54:12 $
*
*
*
@@ -145,7 +145,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.94 $ $Date: 2002/02/11 22:21:58 $
+ * @version $Revision: 1.95 $ $Date: 2002/02/14 19:54:12 $
*/
public class StandardContext
@@ -1212,8 +1212,11 @@
synchronized (applicationListeners) {
String results[] =new String[applicationListeners.length + 1];
-for (int i = 0; i applicationListeners.length; i++)
+for (int i = 0; i applicationListeners.length; i++) {
+if (listener.equals(applicationListeners[i]))
+return;
results[i] = applicationListeners[i];
+}
results[applicationListeners.length] = listener;
applicationListeners = results;
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 3770] - HttpSessionListener.sessionCreated() called twice for each session
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3770. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3770 HttpSessionListener.sessionCreated() called twice for each session [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 20:03 --- I've added a chack which should prevent registering the same listener twice. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6199] - resetBuffer doesn't seem to reset buffer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6199. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6199 resetBuffer doesn't seem to reset buffer [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Component|Catalina|Jasper Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 20:21 --- This works with servlets. $8.3 in the JSP spec states that the JSP buffer is separate from the servlet buffer, so I think it's normal that this doesn't do anything in JSPs. JSP experts, feel free to confirm this :) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat 4.0.2 compiling the source for client auth ?
Hi I know in the tomcat 4.0.2 source code, the line in SSLServerSocketFactory.java for enabling the trustManagerFactory is commented out this disabling the client authentication capability. // Create the trust manager factory used for checking certificates /* trustManagerFactory = TrustManagerFactory.getInstance(algorithm); trustManagerFactory.init(keyStore); */ Is this functionality definitely unusable at the moment ? Is it possible to uncomment the lines and recompile with the TrustManagerFactory to enable client authentication ? Any anticipated timeline when 4.0 client authentication will be enabled. Any info/direction would be greatly appreciated as we are trying to do client authenication with tomcat standalone without having to go the apache/tomcat router. Many Thanks Stephen [EMAIL PROTECTED] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5852] - SessionCreated called twice
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5852. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5852 SessionCreated called twice [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 20:41 --- I tested with the examples webapp (it includes a session listener exmaple which logs the events), and there are no extra sessionCreated events. sessionDidActivate (and its opposite) is called on the attributes bound with the session if they implement HttpSessionActivationListener. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/admin/host - New directory
manveen 02/02/14 12:33:26 jakarta-tomcat-4.0/webapps/admin/host - New directory -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/admin/service service.jsp
manveen 02/02/14 12:37:22 Modified:webapps/admin server.jsp webapps/admin/WEB-INF struts-config.xml webapps/admin/WEB-INF/classes/org/apache/webapp/admin ServerAction.java SetUpServerAction.java webapps/admin/WEB-INF/classes/org/apache/webapp/admin/host HostForm.java SetUpHostAction.java webapps/admin/WEB-INF/classes/org/apache/webapp/admin/service DeleteServiceAction.java ServiceAction.java ServiceForm.java webapps/admin/service service.jsp Added: webapps/admin/WEB-INF/classes/org/apache/webapp/admin/host DeleteHostAction.java DeleteHostForm.java SetUpDeleteHostAction.java webapps/admin/host deleteHost.jsp host.jsp Removed: webapps/admin host.jsp Log: * Added functionality to be able to list hosts and selectively delete Hosts from the admin tool. * Log appropriate error meeasges in case of problems getting/setting attributes on server mBean. Revision ChangesPath 1.10 +2 -2 jakarta-tomcat-4.0/webapps/admin/server.jsp Index: server.jsp === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/admin/server.jsp,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- server.jsp13 Feb 2002 00:03:32 - 1.9 +++ server.jsp14 Feb 2002 20:37:21 - 1.10 @@ -39,7 +39,7 @@ /table %@ include file=buttons.jsp % -br + br table class=back-table border=0 cellspacing=0 cellpadding=1 width=100% tr @@ -64,7 +64,7 @@ html:select property=debugLvl bean:define id=debugLvlVals name=serverForm property=debugLvlVals/ html:options collection=debugLvlVals property=value - labelProperty=label/ + labelProperty=label/ /html:select /controls:data /controls:row 1.31 +25 -2 jakarta-tomcat-4.0/webapps/admin/WEB-INF/struts-config.xml Index: struts-config.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/struts-config.xml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- struts-config.xml 13 Feb 2002 21:37:44 - 1.30 +++ struts-config.xml 14 Feb 2002 20:37:21 - 1.31 @@ -39,6 +39,10 @@ form-bean name=hostForm type=org.apache.webapp.admin.host.HostForm/ +!-- Delete Host form bean -- +form-bean name=deleteHostForm +type=org.apache.webapp.admin.host.DeleteHostForm/ + !-- Context form bean -- form-bean name=contextForm type=org.apache.webapp.admin.context.ContextForm/ @@ -138,7 +142,11 @@ redirect=false/ forwardname=Host -path=/host.jsp +path=/host/host.jsp +redirect=false/ + +forwardname=Delete Host +path=/host/deleteHost.jsp redirect=false/ forwardname=Context @@ -296,6 +304,13 @@ scope=session /action +!-- Set up delete Host datastructure -- +actionpath=/setUpDeleteHost + type=org.apache.webapp.admin.host.SetUpDeleteHostAction + name=deleteHostForm + scope=session +/action + !-- Set up Context datastructure -- actionpath=/setUpContext type=org.apache.webapp.admin.context.SetUpContextAction @@ -375,7 +390,15 @@ type=org.apache.webapp.admin.host.HostAction name=hostForm scope=session - input=/host.jsp + input=/host/host.jsp +/action + +!-- Process a delete host change -- +actionpath=/deleteHost + type=org.apache.webapp.admin.host.DeleteHostAction + name=deleteHostForm + scope=session + input=/host/deleteHost.jsp /action !-- Process a context change -- 1.5 +5 -5 jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/ServerAction.java Index: ServerAction.java === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/ServerAction.java,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- ServerAction.java 13 Feb 2002 22:07:53 -
DO NOT REPLY [Bug 6341] - tomcat dies on startup
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6341. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6341 tomcat dies on startup --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 20:54 --- I meant I'm happy to test on Mac Classic OS, not Mac OS X (see previous comment). The problem is Classic specific. Tomcat runs fine on X for me. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tomcat 4.0.2 compiling client auth source ?
Hi I know in the tomcat 4.0.2 source code, the line in SSLServerSocketFactory.java for enabling the trustManagerFactory is commented out this disabling the client authentication capability. // Create the trust manager factory used for checking certificates /* trustManagerFactory = TrustManagerFactory.getInstance(algorithm); trustManagerFactory.init(keyStore); */ Is this functionality definitely unusable at the moment ? Is it possible to uncomment the lines and recompile with the TrustManagerFactory to enable client authentication ? Any anticipated timeline when 4.0 client authentication will be enabled. Any info/direction would be greatly appreciated as we are trying to do client authenication with tomcat standalone without having to go the apache/tomcat router. Many Thanks Stephen [EMAIL PROTECTED] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6476] New: - error with loading webapp when using certain libs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6476. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6476 error with loading webapp when using certain libs Summary: error with loading webapp when using certain libs Product: Tomcat 4 Version: 4.0.1 Final Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have the following java jar files in my WEB-INF/lib directory: jaxp_1.1.jar jdom.jar xalan_2.1.jar xerces.jar Every time my web application attempts to startup (when tomcat starts up) I get the following error messages: 2002-02-14 16:15:44 StandardContext[/mywebapp]: Servlet /mywebapp threw load() exception javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:871) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3267 ) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3384) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:454) at org.apache.catalina.core.StandardHost.install(StandardHost.java:712) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:599) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:777) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:463) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.ja va:155) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1131) at org.apache.catalina.core.StandardHost.start(StandardHost.java:612) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:307) at org.apache.catalina.core.StandardService.start(StandardService.java:388) at org.apache.catalina.core.StandardServer.start(StandardServer.java:505) at org.apache.catalina.startup.Catalina.start(Catalina.java:776) at org.apache.catalina.startup.Catalina.execute(Catalina.java:681) at org.apache.catalina.startup.Catalina.process(Catalina.java:179) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243) - Root Cause - java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java :139) at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserUtils.java:183) at org.apache.jasper.compiler.TldLocationsCache.processWebDotXml(TldLocationsCache. java:165) at org.apache.jasper.compiler.TldLocationsCache.init(TldLocationsCache.java:138) at org.apache.jasper.EmbededServletOptions.init(EmbededServletOptions.java:324) at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:266) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:852) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3267 ) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3384) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:454) at org.apache.catalina.core.StandardHost.install(StandardHost.java:712) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:599) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:777) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:463) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.ja va:155) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1131) at org.apache.catalina.core.StandardHost.start(StandardHost.java:612) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:307) at org.apache.catalina.core.StandardService.start(StandardService.java:388) at org.apache.catalina.core.StandardServer.start(StandardServer.java:505) at org.apache.catalina.startup.Catalina.start(Catalina.java:776) at org.apache.catalina.startup.Catalina.execute(Catalina.java:681) at
Tomcat 3.3.1 Beta 1 Released
The first beta release of Tomcat 3.3.1 is available for download. This release contains many bug fixes and a number of small feature additions. It continues to be a Servlet 2.2/JSP 1.1 reference implementation. The differences from Tomcat 3.3(a) are documented here: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1-b1/RELEASE-NOTES-3.3.1.txt The source and binary distributions may be found at: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1-b1/ The RPMs are not yet available, but should be available soon. The online documentation found at: http://jakarta.apache.org/tomcat/tomcat-3.3-doc/index.html includes information related to this release. To log problems or bugs, as well as submit patches, please refer to: http://jakarta.apache.org/site/bugs.html When logging bugs to Bugzilla, please specify the Product as Tomcat 3 and the Version as 3.3.1 Beta 1. Also, supplying a test case will greatly improve our ability to address the problem. Please do so if at all possible. Thanks, Larry Isaacs -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6279] - Resubmit to j_security_check mistakenly fetches a page of that name
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6279. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6279 Resubmit to j_security_check mistakenly fetches a page of that name --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 22:09 --- 4.0.2 still exhibits this behavior. our testing has uncovered this problem too. jetty seems to do it just fine. going back and resubmitting against jetty just proceeds as we would expect as the new user. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6450] - error-by-one in partial HTTP/1.1 GET requests
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6450. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6450 error-by-one in partial HTTP/1.1 GET requests --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 22:30 --- Thanks for your speedy reply! This fix is very gratifying! You've just become my short-duration-personal-saviour! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6476] - error with loading webapp when using certain libs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6476. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6476 error with loading webapp when using certain libs [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 23:16 --- There is a fix for this in the 4.0.2 release (but unfortunately the fix will cause problems with Xalan; see bug 6374). *** This bug has been marked as a duplicate of 6248 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6248] - using xerces in webapp causes class cast exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6248. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6248 using xerces in webapp causes class cast exception [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 23:16 --- *** Bug 6476 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6478] New: - Default Tomcat Encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6478. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6478 Default Tomcat Encoding Summary: Default Tomcat Encoding Product: Tomcat 3 Version: 3.2.3 Final Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Encoding AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Currently the encoding used for both requests and responses to/from Tomcat are by default ISO-8859-1. What I would like to do is be able to specify the character encoding that Tomcat should use for requests responses to be UTF- 8. One way to accommodate this is to provided a way of specifying the encoding (defaults to ISO-8859-1 for backward compatibility) and modify RequestImpl.handleParameters to process the query string into the desired encoding and assign the content type in ResponseImpl specify charset=encoding. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6411] - HttpSession.isNew() always returns false
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6411. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6411 HttpSession.isNew() always returns false [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 23:41 --- Tried with the session example, and it works for me (try adding debug statements), even when the first request is a POST. If your test case is different, please submit it. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/loader WebappLoader.java
remm02/02/14 16:02:28
Modified:catalina/src/share/org/apache/catalina/loader
WebappLoader.java
Log:
- Clean the start and stop methods of context.
- I think it's not doable to take advantage of the inheritance from ContainerBase
for these two methods, as the StandardContext must take care of the context class
laoder
binding (and putting it at the end of Loader.start was a hack), so it's necessary
to
interleave method calls.
- The shutdown order is also modified, and the manager can now notify
the session listeners if needed.
Revision ChangesPath
1.25 +4 -6
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/loader/WebappLoader.java
Index: WebappLoader.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/loader/WebappLoader.java,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- WebappLoader.java 12 Feb 2002 20:43:33 - 1.24
+++ WebappLoader.java 15 Feb 2002 00:02:28 - 1.25
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/loader/WebappLoader.java,v
1.24 2002/02/12 20:43:33 remm Exp $
- * $Revision: 1.24 $
- * $Date: 2002/02/12 20:43:33 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/loader/WebappLoader.java,v
1.25 2002/02/15 00:02:28 remm Exp $
+ * $Revision: 1.25 $
+ * $Date: 2002/02/15 00:02:28 $
*
*
*
@@ -117,7 +117,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.24 $ $Date: 2002/02/12 20:43:33 $
+ * @version $Revision: 1.25 $ $Date: 2002/02/15 00:02:28 $
*/
public class WebappLoader
@@ -645,8 +645,6 @@
// Binding the Webapp class loader to the directory context
DirContextURLStreamHandler.bind
((ClassLoader) classLoader, this.container.getResources());
-
-Thread.currentThread().setContextClassLoader(classLoader);
} catch (Throwable t) {
throw new LifecycleException(start: , t);
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core StandardContext.java
remm02/02/14 16:03:28
Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
Log:
- Clean the start and stop methods of context.
- I think it's not doable to take advantage of the inheritance from ContainerBase
for these two methods, as the StandardContext must take care of the context class
laoder
binding (and putting it at the end of Loader.start was a hack), so it's necessary
to
interleave method calls.
- The shutdown order is also modified, and the manager can now notify
the session listeners if needed.
- Note: I've tested with the tester.
Revision ChangesPath
1.96 +123 -12
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java
Index: StandardContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -r1.95 -r1.96
--- StandardContext.java 14 Feb 2002 19:54:12 - 1.95
+++ StandardContext.java 15 Feb 2002 00:03:28 - 1.96
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.95 2002/02/14 19:54:12 remm Exp $
- * $Revision: 1.95 $
- * $Date: 2002/02/14 19:54:12 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.96 2002/02/15 00:03:28 remm Exp $
+ * $Revision: 1.96 $
+ * $Date: 2002/02/15 00:03:28 $
*
*
*
@@ -114,6 +114,7 @@
import org.apache.catalina.LifecycleException;
import org.apache.catalina.LifecycleListener;
import org.apache.catalina.Loader;
+import org.apache.catalina.Mapper;
import org.apache.catalina.Request;
import org.apache.catalina.Response;
import org.apache.catalina.Wrapper;
@@ -145,7 +146,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.95 $ $Date: 2002/02/14 19:54:12 $
+ * @version $Revision: 1.96 $ $Date: 2002/02/15 00:03:28 $
*/
public class StandardContext
@@ -2394,9 +2395,8 @@
if (context != null)
context.clearAttributes();
-// Shut down filters and application event listeners
+// Shut down filters
filterStop();
-listenerStop();
// Shut down our session manager
if ((manager != null) (manager instanceof Lifecycle)) {
@@ -2407,6 +2407,9 @@
}
}
+// Shut down application event listeners
+listenerStop();
+
if (isUseNaming()) {
// Start
namingContextListener.lifecycleEvent
@@ -3302,6 +3305,10 @@
*/
public synchronized void start() throws LifecycleException {
+if (started)
+throw new LifecycleException
+(sm.getString(containerBase.alreadyStarted, logName()));
+
if (debug = 1)
log(Starting);
if (debug = 1)
@@ -3370,13 +3377,62 @@
// Standard container startup
if (debug = 1)
log(Processing standard container startup);
+
if (ok) {
+
try {
-super.start();
+
+addDefaultMapper(this.mapperClass);
+started = true;
+
+// Start our subordinate components, if any
+if ((loader != null) (loader instanceof Lifecycle))
+((Lifecycle) loader).start();
+if ((logger != null) (logger instanceof Lifecycle))
+((Lifecycle) logger).start();
+
+// Unbinding thread
+unbindThread(oldCCL);
+
+// Binding thread
+oldCCL = bindThread();
+
+if ((manager != null) (manager instanceof Lifecycle))
+((Lifecycle) manager).start();
+if ((cluster != null) (cluster instanceof Lifecycle))
+((Lifecycle) cluster).start();
+if ((realm != null) (realm instanceof Lifecycle))
+((Lifecycle) realm).start();
+if ((resources != null) (resources instanceof Lifecycle))
+((Lifecycle) resources).start();
+
+// Start our Mappers, if any
+Mapper mappers[] = findMappers();
+for (int i = 0; i mappers.length; i++) {
+if (mappers[i] instanceof Lifecycle)
+((Lifecycle) mappers[i]).start();
+}
+
+// Start our child containers, if any
+Container children[] =
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans mbeans-descriptors.xml
craigmcc02/02/14 16:19:27 Modified:catalina/src/share/org/apache/catalina/mbeans mbeans-descriptors.xml Log: Add a descriptor for CertificatesValve. Revision ChangesPath 1.31 +20 -1 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/mbeans-descriptors.xml Index: mbeans-descriptors.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/mbeans-descriptors.xml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- mbeans-descriptors.xml14 Feb 2002 07:47:14 - 1.30 +++ mbeans-descriptors.xml15 Feb 2002 00:19:27 - 1.31 @@ -6,7 +6,7 @@ !-- Descriptions of JMX MBeans for Catalina - $Id: mbeans-descriptors.xml,v 1.30 2002/02/14 07:47:14 amyroh Exp $ + $Id: mbeans-descriptors.xml,v 1.31 2002/02/15 00:19:27 craigmcc Exp $ -- mbeans-descriptors @@ -148,6 +148,25 @@ entropy of the initialization of our random number generator type=java.lang.String/ + /mbean + + + mbean name=CertificatesValve +className=org.apache.catalina.mbeans.ClassNameMBean + description=Valve that exposes SSL certificate information + domain=Catalina +group=Valve + type=org.apache.catalina.valves.CertificatesValve + +attribute name=className + description=Fully qualified class name of the managed object + type=java.lang.String +writeable=false/ + +attribute name=debug + description=The debugging detail level for this component + type=int/ + /mbean -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6219] - FORM authentication does not work when using AJP connector to IIS (tested in 4.0.1 and 4.0.2b2)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6219.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6219
FORM authentication does not work when using AJP connector to IIS (tested in 4.0.1 and
4.0.2b2)
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution||DUPLICATE
--- Additional Comments From [EMAIL PROTECTED] 2002-02-15 00:38 ---
Thanks for finding this Marcin.
I've replaced the code with the following and it seems to fix the problem. This
looks like the same bug as #5647 and this fix seems to fix both of them.
I'll post the fix to the news group so it gets tested and added by one of the
committers.
Replace from line 115:
// String remoteUser = ajp.remoteUser().toString();
// if(remoteUser != null)
// setUserPrincipal(new Ajp13Principal(remoteUser));
String remoteUser = ajp.remoteUser().toString();
if ((remoteUser != null) (! remoteUser.equals ()))
{
setUserPrincipal(new Ajp13Principal(remoteUser));
}
else
{
setUserPrincipal(null);
}
-Jonathan
*** This bug has been marked as a duplicate of 5647 ***
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5647] - AJP13 connector will not pass authentication requests
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5647. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5647 AJP13 connector will not pass authentication requests [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-02-15 00:38 --- *** Bug 6219 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Fix for AJP13 Connector Authentication Bug !!!
I've confirmed the fix for the AJP13 Connector / Authentication problem in
4.0.2.
This solves high priority bugs 5647 and 6219.
Please have one of the committers confirm the fix and check it in to cvs.
The issue was reported in Bug 6219.
I tested the following modification and it seems to resolve the problem.
The problem is in org.apache.ajp.tomcat4.Ajp13Request.setAjpRequest The fix is
below:
Replace from line 115:
// String remoteUser = ajp.remoteUser().toString();
// if(remoteUser != null)
// setUserPrincipal(new Ajp13Principal(remoteUser));
String remoteUser = ajp.remoteUser().toString();
if ((remoteUser != null) (! remoteUser.equals ()))
{
setUserPrincipal(new Ajp13Principal(remoteUser));
}
else
{
setUserPrincipal(null);
}
After making this modification, I am able to successfully serve the protected
example url through the IIS connector and get properly challenged by the login
screen and am able to login and logout as expected.
http://localhost/examples/jsp/security/protected/index.jsp
-Jonathan
This email and any files transmitted with it are for the named person's use
only. It may contain confidential, proprietary or legally privileged
information. No confidentiality or privilege is waived or lost by any
mistransmission. If you receive this message in error, please immediately
delete it and all copies of it from your system, destroy any hard copies
of it and notify the sender. You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you
are not the intended recipient.
This email message has been swept by a virus software product for the
presence of computer viruses.
*
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6331] - Cannot add more than one cookie
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6331. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6331 Cannot add more than one cookie [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-02-15 00:47 --- I created a servlet with the following in the service method: res.setContentLength(0); HttpSession session = req.getSession(true); res.addCookie(new Cookie(fred, wilma)); res.addCookie(new Cookie(barney, betty)); With a telnet: GET /examples/servlet/Void HTTP/1.1 Host: localhost Response is: HTTP/1.1 200 OK Content-Length: 0 Date: Fri, 15 Feb 2002 00:42:10 GMT Server: Apache Tomcat/4.1-dev (HTTP/1.1 Connector) Set-Cookie: fred=wilma Set-Cookie: barney=betty Set-Cookie: JSESSIONID=CEE24AF0AE8AF081E3107AA036636267;Path=/examples The result was tested with either the 4.0 branch or the HEAD branch. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5647] - AJP13 connector will not pass authentication requests
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5647.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5647
AJP13 connector will not pass authentication requests
--- Additional Comments From [EMAIL PROTECTED] 2002-02-15 00:50 ---
I've confirmed the fix for the AJP13 Connector / Authentication problem in
4.0.2.
This solves high priority bugs 5647 and 6219.
Please have one of the committers confirm the fix and check it in to cvs.
The issue was reported in Bug 6219.
I tested the following modification and it seems to resolve the problem.
The problem is in org.apache.ajp.tomcat4.Ajp13Request.setAjpRequest The fix is
below:
Replace from line 115:
// String remoteUser = ajp.remoteUser().toString();
// if(remoteUser != null)
// setUserPrincipal(new Ajp13Principal(remoteUser));
String remoteUser = ajp.remoteUser().toString();
if ((remoteUser != null) (! remoteUser.equals ()))
{
setUserPrincipal(new Ajp13Principal(remoteUser));
}
else
{
setUserPrincipal(null);
}
After making this modification, I am able to successfully serve the protected
example url through the IIS connector and get properly challenged by the login
screen and am able to login and logout as expected.
http://localhost/examples/jsp/security/protected/index.jsp
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4 Ajp13Request.java
remm02/02/14 16:54:43
Modified:jk/java/org/apache/ajp/tomcat4 Ajp13Request.java
Log:
- Apply fix for 5647 and 6219.
- Patch submitted by Jonathan Pierce jonathan.pierce at seagram.com
Revision ChangesPath
1.7 +3 -1
jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/Ajp13Request.java
Index: Ajp13Request.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/Ajp13Request.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Ajp13Request.java 31 Jan 2002 17:18:51 - 1.6
+++ Ajp13Request.java 15 Feb 2002 00:54:43 - 1.7
@@ -113,8 +113,10 @@
setServerPort(ajp.getServerPort());
String remoteUser = ajp.remoteUser().toString();
-if (remoteUser != null) {
+if ((remoteUser != null) (!(remoteUser.equals( {
setUserPrincipal(new Ajp13Principal(remoteUser));
+} else {
+setUserPrincipal(null);
}
setAuthType(ajp.authType().toString());
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4 Ajp13Request.java
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: viernes 15 de febrero de 2002 1:55 Perhaps is better to have explicit control over that, to disable or enable the control of the native auth honoring..the infamous tomcatAuthentication attribute.. Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4 Ajp13Request.java
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: viernes 15 de febrero de 2002 1:55 Perhaps is better to have explicit control over that, to disable or enable the control of the native auth honoring..the infamous tomcatAuthentication attribute.. I don't quite understand, as the patch only add filtering out an empty string, right ? Or did I miss something ? In any case, I just applied the patch as it looked ok to me. If the patch is bad, revert it. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4 Ajp13Request.java
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: viernes 15 de febrero de 2002 1:55 Perhaps is better to have explicit control over that, to disable or enable the control of the native auth honoring..the infamous tomcatAuthentication attribute.. I don't quite understand, as the patch only add filtering out an empty string, right ? Or did I miss something ? In any case, I just applied the patch as it looked ok to me. If the patch is bad, revert it. i think native auth honoring is different than the problem this patch addresses. i don't think the patch should be reverted (so long as it works :)). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Fix for AJP13 Connector Authentication Bug !!!
i've tested the patch remy checked in and it's now working for me too. very cool.
thanks guys :)
-Original Message-
From: Jonathan Pierce [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 6:40 PM
To: [EMAIL PROTECTED]
Subject: Fix for AJP13 Connector Authentication Bug !!!
I've confirmed the fix for the AJP13 Connector /
Authentication problem in
4.0.2.
This solves high priority bugs 5647 and 6219.
Please have one of the committers confirm the fix and check
it in to cvs.
The issue was reported in Bug 6219.
I tested the following modification and it seems to resolve
the problem.
The problem is in
org.apache.ajp.tomcat4.Ajp13Request.setAjpRequest The fix is
below:
Replace from line 115:
// String remoteUser = ajp.remoteUser().toString();
// if(remoteUser != null)
// setUserPrincipal(new Ajp13Principal(remoteUser));
String remoteUser = ajp.remoteUser().toString();
if ((remoteUser != null) (! remoteUser.equals ()))
{
setUserPrincipal(new Ajp13Principal(remoteUser));
}
else
{
setUserPrincipal(null);
}
After making this modification, I am able to successfully
serve the protected
example url through the IIS connector and get properly
challenged by the login
screen and am able to login and logout as expected.
http://localhost/examples/jsp/security/protected/index.jsp
-Jonathan
**
**
This email and any files transmitted with it are for the
named person's use
only. It may contain confidential, proprietary or legally privileged
information. No confidentiality or privilege is waived or lost by any
mistransmission. If you receive this message in error,
please immediately
delete it and all copies of it from your system, destroy any
hard copies
of it and notify the sender. You must not, directly or
indirectly, use,
disclose, distribute, print, or copy any part of this message if you
are not the intended recipient.
This email message has been swept by a virus software product for the
presence of computer viruses.
**
***
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util IntrospectionUtils.java
billbarker02/02/14 18:43:52
Modified:src/share/org/apache/tomcat/util IntrospectionUtils.java
Log:
Fix Tomcat for Mac OS.
Use File.getParent instead of .. to get the parent directory (since not all OSs
know about ..). Based on suggestion from Martin Redington.
Fix for bug #6341
Reported by: Martin Redington [EMAIL PROTECTED]
Revision ChangesPath
1.18 +8 -2
jakarta-tomcat/src/share/org/apache/tomcat/util/IntrospectionUtils.java
Index: IntrospectionUtils.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/IntrospectionUtils.java,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- IntrospectionUtils.java 5 Feb 2002 01:32:05 - 1.17
+++ IntrospectionUtils.java 15 Feb 2002 02:43:52 - 1.18
@@ -189,7 +189,10 @@
home=new File(./).getCanonicalPath();
}
File f=new File( home );
- File f1=new File ( f, ..);
+ String parentDir = f.getParent();
+ if(parentDir == null)
+ parentDir = home; // unix style
+ File f1=new File ( parentDir );
install = f1.getCanonicalPath();
if( installSysProp != null )
System.getProperties().put( installSysProp, install );
@@ -204,7 +207,10 @@
if( new File( fname ).exists()) {
try {
File f=new File( path );
- File f1=new File ( f, ..);
+ String parentDir = f.getParent();
+ if( parentDir == null )
+ parentDir = path; // unix style
+ File f1=new File ( parentDir );
install = f1.getCanonicalPath();
if( installSysProp != null )
System.getProperties().put( installSysProp,
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6341] - tomcat dies on startup
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6341. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6341 tomcat dies on startup [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-15 02:45 --- This is now fixed in the CVS HEAD, and should appear in tonight's nightly (which is pretty much 3.3.1-B1 + this fix). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.1.txt
billbarker02/02/14 18:47:14 Modified:.RELEASE-NOTES-3.3.1.txt Log: Document fix to 6341 Revision ChangesPath 1.35 +3 -1 jakarta-tomcat/RELEASE-NOTES-3.3.1.txt Index: RELEASE-NOTES-3.3.1.txt === RCS file: /home/cvs/jakarta-tomcat/RELEASE-NOTES-3.3.1.txt,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- RELEASE-NOTES-3.3.1.txt 11 Feb 2002 12:41:00 - 1.34 +++ RELEASE-NOTES-3.3.1.txt 15 Feb 2002 02:47:14 - 1.35 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-3.3.1.txt,v 1.34 2002/02/11 12:41:00 larryi Exp $ +$Id: RELEASE-NOTES-3.3.1.txt,v 1.35 2002/02/15 02:47:14 billbarker Exp $ This document describes the changes that have been made since the @@ -267,6 +267,8 @@ 6137 Fix the admin webapp to be more careful when using the remove-context feature. Also, the boxes were mis-labeled. + +6341 Fix the guess home logic so that it can work on Mac OS Connectors: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4 Ajp13Request.java
It's a trust issue. By default, 3.3 doesn't trust IIS's/Apache's authentication and will check it again. I agree that we should implement tomcatAuth in 4.0.3 if at all. - Original Message - From: Kevin Seguin [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Thursday, February 14, 2002 6:18 PM Subject: RE: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4 Ajp13Request.java De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: viernes 15 de febrero de 2002 1:55 Perhaps is better to have explicit control over that, to disable or enable the control of the native auth honoring..the infamous tomcatAuthentication attribute.. I don't quite understand, as the patch only add filtering out an empty string, right ? Or did I miss something ? In any case, I just applied the patch as it looked ok to me. If the patch is bad, revert it. i think native auth honoring is different than the problem this patch addresses. i don't think the patch should be reverted (so long as it works :)). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5330] - JNDI ENC context problem.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5330. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5330 JNDI ENC context problem. --- Additional Comments From [EMAIL PROTECTED] 2002-02-15 04:13 --- I tested it tonight. Everything work now. Good job, thank you. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6480] New: - HttpServletRequest.getPathTranslated() returns different results on repeated actions
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6480. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6480 HttpServletRequest.getPathTranslated() returns different results on repeated actions Summary: HttpServletRequest.getPathTranslated() returns different results on repeated actions Product: Tomcat 4 Version: 4.0 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi there, I have created a HTML file which uses GET method and the Query String looks like this /servlet/hello/empty.txt . A servlet aliased hello takes the request and when I try to print the HttpServletRequest.getPathInfo() and HttpServletRequest.getPathTranslated() it prints Path Info == /empty.txt Translated Path Info == D:\Program Files\Apache Tomcat 4.0 \webapps\ROOT\hello\empty.txt which is correct and when I do this again for a second attempt I get a different Output Path Info == /empty.txt Translated Path Info == D:\Program Files\Apache Tomcat 4.0 \webapps\ROOT\empty.txt I don't understand why it gives me correct path the very first time and different wrong path the next time I do the same. I have the directory structure set up under ROOT\hello\empty.txt. I am not sure If I am doing something wrong or if this a BUG. If you need more info I can send the files under my ROOT directories. thanks Amar. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6201] - ISO-8859-8-i problem. (hebrew)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6201. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6201 ISO-8859-8-i problem. (hebrew) --- Additional Comments From [EMAIL PROTECTED] 2002-02-15 05:14 --- Would it be possible for you to provide an example page that we can test with? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
