Re: Bug ordering

Welcome on board! To answer your questions: - The submitter initially sets the "severity" and "priority" fields, but they can be subsequently modified by anyone. - "other" means that the submitter didn't bother to set it. - See . The "votes" are m

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_config.c jk_env.c

costin 02/03/24 19:35:11 Modified:jk/native2/common jk_config.c jk_env.c Log: Moved the create method, use the more acurate method to extract the object type. Revision ChangesPath 1.6 +6 -54 jakarta-tomcat-connectors/jk/native2/common/jk_config.c Index:

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_ajp13.c

costin 02/03/24 19:34:38 Modified:jk/native2/common jk_worker_ajp13.c Log: Magic to set the channel. The worker.init() will create a channel automatically if none is specified. ( it'll be better to configure the channel and create the worker automatically ) Revision

cvs commit: jakarta-tomcat-connectors/jk/native2/include jk_env.h

costin 02/03/24 19:32:35 Modified:jk/native2/include jk_env.h Log: Added a better creation method ( moved from jk_config ), easier to use. It uses the full name and return the jk_bean ( to be used for futher config ) Revision ChangesPath 1.10 +12 -1 jakarta-t

cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache13 mod_jk2.c

costin 02/03/24 19:31:41 Modified:jk/native2/server/apache13 mod_jk2.c Log: Fix init, post_config doesn't exist in 1.3 Revision ChangesPath 1.7 +3 -12 jakarta-tomcat-connectors/jk/native2/server/apache13/mod_jk2.c Index: mod_jk2.c ==

cvs commit: jakarta-tomcat-connectors/jk/doc/jk2 jk2.html

costin 02/03/24 19:30:10 Modified:jk/doc/jk2 jk2.html Log: A small list of unresolved problems. Revision ChangesPath 1.3 +218 -183 jakarta-tomcat-connectors/jk/doc/jk2/jk2.html Index: jk2.html ===

DO NOT REPLY [Bug 7191] - Tomcat 4 cannot handle JSP with utf-8 contentType header

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: servlet.jar, /ext, MANIFEST.MF

Christopher, Let me try this out later this week. I will let you know if the hack works. Also, even if the hack does not check the version info of servlet.jar, I see know harm in adding it. Patrick "Christopher K. St. John" wrote: > > Patrick Luby wrote: > > > > I can't help but think that th

Re: servlet.jar, /ext, MANIFEST.MF

Patrick Luby wrote: > > I can't help but think that there might be a way to point Tomcat > to its bundled jars without losing access to any non-conflicting > extensions. That would be better. (but the servletapi still should have the appropriate version info :-) > ... have the class loaders

DO NOT REPLY [Bug 6402] - JNDIRealm, LDAP and SHA passwords vs {SHA}Base64Coded= passwords

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context AddContextAction.java

manveen 02/03/24 13:41:58 Added: webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context AddContextAction.java Log: Added implementation of add context operation. Revision ChangesPath 1.1 jakarta-tomcat-4.0/webapps/admin/

Re: servlet.jar, /ext, MANIFEST.MF

Christopher, "Christopher K. St. John" wrote: > That seems a bit hostile. The majority of stuff that could > go into /ext is harmless. Ignoring it punishes users who > correctly install the "right" extensions. You have a good point. Using "-Djava.ext.dirs=" is an all or nothing approach and may

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_channel_socket.c jk_config.c jk_env.c jk_uriEnv.c jk_worker_ajp13.c jk_worker_status.c

costin 02/03/24 11:24:26 Modified:jk/native2/common jk_channel_socket.c jk_config.c jk_env.c jk_uriEnv.c jk_worker_ajp13.c jk_worker_status.c Log: Small fixes, cosmetic changes, move closer to the target documented behavior. ( hopefully the implemented rea

cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2 jk_service_apache2.c

costin 02/03/24 11:22:19 Modified:jk/native2/server/apache13 jk_service_apache13.c jk/native2/server/apache2 jk_service_apache2.c Log: Fix - the headers are dumped for debugging, but only the first time. Revision ChangesPath 1.3 +11 -13 jakarta-

cvs commit: jakarta-tomcat-connectors/jk/native2/include jk_env.h

costin 02/03/24 11:21:40 Modified:jk/native2/include jk_env.h Log: Initial/experimental field to store all the supported properties in each component. Will be used to simplify/generalize the status worker. Revision ChangesPath 1.9 +8 -0 jakarta-tomcat-

cvs commit: jakarta-tomcat-connectors/jk/doc/jk2 jk2.properties

costin 02/03/24 11:20:35 Added: jk/doc/jk2 jk2.properties Log: My ( half working - I only tested the ajp13/socket and status ) config file. Will change to match the documentation ( and the documentation will also change to match the feedback you send ) Revision Chang

DO NOT REPLY [Bug 7191] - Tomcat 4 cannot handle JSP with utf-8 contentType header

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: servlet.jar, /ext, MANIFEST.MF

Patrick Luby wrote: > "Christopher K. St. John" wrote: > > But wouldn't that mean that "legitimate" exetensions were > > ignored? > Yes, they would be ignored. That seems a bit hostile. The majority of stuff that could go into /ext is harmless. Ignoring it punishes users who correctly inst

DO NOT REPLY [Bug 7413] - java.io.CharConversionException om file upload, 4.0.4 Beta 2

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4 CoyoteRequest.java

remm02/03/24 10:48:48 Modified:coyote/src/java/org/apache/coyote/tomcat4 CoyoteRequest.java Log: - Don't parse post body unless content-type is URL FORM encoded. - Fix bug 7413. Revision ChangesPath 1.13 +7 -4 jakarta-tomcat-connectors/coyote/src/java/or

cvs commit: jakarta-tomcat-connectors/jk/doc/jk2 jk2.html

costin 02/03/24 10:46:16 Modified:jk/doc/jk2 jk2.html Log: Few updates/fixes. Again, unless someone is -1 or has a different proposal ( expressed by editing this file and changing the C code ) this is what will be used for jk2 config. We may provide a backward compat la

Re: servlet.jar, /ext, MANIFEST.MF

Christopher, "Christopher K. St. John" wrote: > But wouldn't that mean that "legitimate" exetensions were > ignored? > Yes, they would be ignored. Although this is a limitation, it might be a reasonable one when you consider all the potential problems that can be caused by putting XML parsers,

Re: servlet.jar, /ext, MANIFEST.MF

Patrick Luby wrote: > > we can put "-Djava.ext.dirs=" as an argument in the Tomcat scripts. > This argument causes the JVM to ignore any jars in its jre/lib/ext > directory ... > But wouldn't that mean that "legitimate" exetensions were ignored? -- Christopher St. John [EMAIL PROTECTED] D

Re: servlet.jar, /ext, MANIFEST.MF

Christopher, There is an easier solution, although it has limits. Since the Tomcat binaries include servlet.jar, we can put "-Djava.ext.dirs=" as an argument in the Tomcat scripts. This argument causes the JVM to ignore any jars in its jre/lib/ext directory so that there is no conflict between th

Bug report for Tomcat 4 [2002/03/24]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 3 [2002/03/24]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

DO NOT REPLY [Bug 7413] New: - java.io.CharConversionException om file upload, 4.0.4 Beta 2

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

FIXED: Nasty Cookie Bug 6983

Hi, This nasty cookie bug has been detected and fixed (locally only) by me http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6983 My question is to you developers, is how will this be handled in future Tomcat 4.x releases? A configuration flag maybe? Regards Anders -- To unsubscribe, e-mail:

Bug ordering

Hi, I'm interested in getting involved into the Tomcat project. I know the usual recommendation of picking out an open issue, digging into it, and fixing it. And that's exactly what I intend to do. The thing is that I'm not able to see any ordering or prioritization of the bugs in the bug databa

DO NOT REPLY [Bug 5405] - Powered by Tomcat

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu