HTTP/1.1 Request lacking Host Header
According to the HTTP/1.1 RFC (section 14.23) all HTTP/1.1 requests MUST contain a Host header, and all HTTP/1.1 severs MUST respond with a 400 if the Host header is missing from an HTTP/1.1 request. Tomcat 4.0b3 responds with a '200 OK HTTP/1.1' response if I send a the following GET /index.html HTTP/1.1 with no Host: header, Kevin Jones DevelopMentor www.develop.com
cvs commit: jakarta-tomcat/src/doc readme
marcsaeg01/04/30 06:18:59 Modified:.Tag: tomcat_32 RELEASE-NOTES src/doc Tag: tomcat_32 readme Log: Release note updates for beta 4. Revision ChangesPath No revision No revision 1.1.2.5 +6 -1 jakarta-tomcat/Attic/RELEASE-NOTES Index: RELEASE-NOTES === RCS file: /home/cvs/jakarta-tomcat/Attic/RELEASE-NOTES,v retrieving revision 1.1.2.4 retrieving revision 1.1.2.5 diff -u -r1.1.2.4 -r1.1.2.5 --- RELEASE-NOTES 2001/04/08 01:51:05 1.1.2.4 +++ RELEASE-NOTES 2001/04/30 13:18:59 1.1.2.5 @@ -1,4 +1,4 @@ -$Id: RELEASE-NOTES,v 1.1.2.4 2001/04/08 01:51:05 marcsaeg Exp $ +$Id: RELEASE-NOTES,v 1.1.2.5 2001/04/30 13:18:59 marcsaeg Exp $ Release Notes for: @@ -322,6 +322,9 @@ error-page tags in web.xml. (#291) - URL encoded data in servlet paths and path info are now decoded properly. (#657) + - HttpServletRequest.encodeURL() now properly encodes URLs that contain + an anchor but no query string. (#1182) + - Error pages now work in virtual hosts. Jasper - Fix for UnsupportedEncodingException due to UTF8 instead of UTF-8. (#269) @@ -337,6 +340,8 @@ - Fixed the defualt character encoding. The default charset is now ISO-8859-1. (#285) - jsp:plugin was not being expanded correctly. (#467) + - Fixed bug that could cause the body of a JSP page to be exeucted before + or while its jspInit() method was being executed. (#1280) Connectors No revision No revision 1.8.2.17 +6 -1 jakarta-tomcat/src/doc/readme Index: readme === RCS file: /home/cvs/jakarta-tomcat/src/doc/readme,v retrieving revision 1.8.2.16 retrieving revision 1.8.2.17 diff -u -r1.8.2.16 -r1.8.2.17 --- readme2001/04/08 01:51:05 1.8.2.16 +++ readme2001/04/30 13:18:59 1.8.2.17 @@ -1,4 +1,4 @@ -$Id: readme,v 1.8.2.16 2001/04/08 01:51:05 marcsaeg Exp $ +$Id: readme,v 1.8.2.17 2001/04/30 13:18:59 marcsaeg Exp $ Release Notes for: @@ -322,6 +322,9 @@ error-page tags in web.xml. (#291) - URL encoded data in servlet paths and path info are now decoded properly. (#657) + - HttpServletRequest.encodeURL() now properly encodes URLs that contain + an anchor but no query string. (#1182) + - Error pages now work in virtual hosts. Jasper - Fix for UnsupportedEncodingException due to UTF8 instead of UTF-8. (#269) @@ -337,6 +340,8 @@ - Fixed the defualt character encoding. The default charset is now ISO-8859-1. (#285) - jsp:plugin was not being expanded correctly. (#467) + - Fixed bug that could cause the body of a JSP page to be exeucted before + or while its jspInit() method was being executed. (#1280) Connectors
tomcat_32 branch locked
I'm just about to start the tag for Tomcat 3.2.2 beta 4.
Re: ajp13 question
Kevin, Excellent -- something I can actually answer! BTW, I'm cc'ing the list -- let's try to have this conversation on the mailing list. That way, everyone can learn and/or participate. The jvm route, as the AJPv13 doc says: ...is used to support sticky sessions -- associating a user's sesson with a particular Tomcat instance in the presence of multiple, load-balancing servers. Let's say you have a single Apache server feeding multiple TC instances. Once a TC instance starts a session for a user, you want all future requests in that session to be forwarded to that instance (so that session data can be held in memory on that box). Load balancing is done by the jk_lb_worker. In jk_lb_worker.c, l 318, the jvm_route property of the service object is set to the name by which the load balancer knows the particular jk worker (which communicates with a particular TC instance). Assuming that that is then an instance of jk_ajp13_worker, this will then get sent over to the TC instance via jk_ajp13.c (ll. 456-458) (this is documented in AJPv13.html). (BTW, if it's an instance of ajp12, it will still work, but we won't go into that here, since no one is porting ajp12 to TC 4). On the Tomcat side, that jvm route is: - Read out of the packet from Apache (in Ajp13.java) - Stored in the request (also in Ajp13.java) - When the session id cookie is generated (jsessionid=...), the jvmroute is tacked onto the end (after a ';') (in modules/session/SessionIdGenerator, I believe). - This cookie is sent to the browser Then, when the browser sends back the session cookie, it will also be sending back the jvmroute, which is the name by which jk_lb_worker knows the right instance of TC to route to. The jk_lb_worker object then reads that (in get_session_route), and routes that particular request to the proper instance of TC. Phew. Okay, so how to make this work in TC 4? I'm not sure -- as you can see from the above description, it's pretty deep in the internals of TC 3 (in the core request object). If you could store it as an extra attribute of the request object, and then modify whatever code creates the session id, you might be in business. You might also ask the list (which has many TC 4 experts) about the best way to handle this. Basically, though, the path is: - jk_lb_worker knows the name, passes it via the jvmroute attribute to TC. - TC inserts that into the session cookie, which is sent back the browser. - jk_lb_worker reads the name back, and uses that for routing. If you wanted to cheat (fine with me!), you could cut this feature out for now, and get ajp13 working *without* load-balancing (still useful), document that fact, and return to it later (or beg for help to fix it once you get everything else working). To do that, just have TC ignore whatever jvmroute is sent over. Everything but load-balancing should still work just fine. Have fun, -Dan kevin seguin wrote: what is the jvm route attribute for in ajp13? there doesn't appear to be an equivalent to Request.setJvmRoute in catalina... thanks. -- Dan Milstein // [EMAIL PROTECTED]
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
Fine, I'll study it - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: kevin seguin [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 5:53 PM To: [EMAIL PROTECTED] Subject: Re: porting ajp13 to tomcat 4 (was Re: ajp13 question) If you have java ajp13 works in non-balancing mode, you've done the hardest part ! that's encouraging :) that's what i've decided to do. my goal is to first get things working, at least minimally, then i (or someone else) can address load-balancing later. my gut feeling, though, after spending some time on ajp13 and tomcat 4 is it's certainly possible. of course, i'm pretty new to the whole tomcat 4 architecture, so i could be way off :) thanks for the info. btw, i've got ajp13/tomcat 4 about half working (probably the easy half...). Could you send the code, we're interest (at least I) ;) the code isn't real pretty right now. in fact, it's downright ugly! but that's ok, that's what refactoring is for ;) and hopefully, somebody who knows more can help! it's basically based on parts of the http connector, and Ajp13.java/Ajp13Interceptor.java from the 04.27 build of tomcat 3.3. i'm attaching a zip file containing my code. i've make it an ajp subpackage of org.apache.catalina.connector. advice/help is welcome/wanted :) -kevin.
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
On Mon, 30 Apr 2001, GOMEZ Henri wrote: damn! i wasn't expecting that complex of an answer ;) The difficulty is in the difference between TC 3.2/3.3 and 4.0 and the how the connector are written. They're just to highly linked in the tomcat core ! Well, someone can reimplement the protocol ( it's just a protocol ). The 3.3 adapter is not linked to the tomcat core, but more to the low-level objects ( and most of the performance comes from that layer ). In other words - minimal garbage generation, lazy evaluation, and all the stuff. Costin
Re: loader.html
On Mon, 30 Apr 2001, Jones, Kevin wrote: Is this file available? It isn't in the 4.0b3 build nor on CVS! Kevin Jones DevelopMentor www.develop.com Where do you find this filename referenced? I don't recognize it. The closest thing I can think of is the classloaders.html page, which is in source directory catalina/docs/dev (or visible in the installed root web application, under Catalina Documentation -- Developer Documentation). Craig
Re: porting ajp13 to tomcat 4 (was Re: ajp13 question)
On Mon, 30 Apr 2001, GOMEZ Henri wrote: damn! i wasn't expecting that complex of an answer ;) The difficulty is in the difference between TC 3.2/3.3 and 4.0 and the how the connector are written. They're just to highly linked in the tomcat core ! Well, someone can reimplement the protocol ( it's just a protocol ). The 3.3 adapter is not linked to the tomcat core, but more to the low-level objects ( and most of the performance comes from that layer ). In other words - minimal garbage generation, lazy evaluation, and all the stuff. Unless everyone's in a hurry to port mod_jk on TC 4 ASAP, I suggest waiting a bit. I'll be spending time on a new connector architecture for TC 4 which will actually be very similar to the one in TC 3.3 (except hopefully even cleaner and simpler). That should make porting mod_jk much easier if there are still people who want to do that. Remy
Re: porting ajp13 to tomcat 4 (was Re: ajp13 question)
Unless everyone's in a hurry to port mod_jk on TC 4 ASAP, I suggest waiting a bit. I'll be spending time on a new connector architecture for TC 4 which will actually be very similar to the one in TC 3.3 (except hopefully even cleaner and simpler). That should make porting mod_jk much easier if there are still people who want to do that. unfortunately, i have an immediate need for ajp13 in tomcat 4. i want to move to tomcat 4, but can't without connectivity between iis/netscape web servers and tomcat. porting ajp13 from tomcat 3.x to tomcat 4 seemed like it would be easier than writing iis/netscape connectors for the new webapp/warp stuff. especially since webapp seems to be a moving target -kevin.
Re: porting ajp13 to tomcat 4 (was Re: ajp13 question)
for those who are interested... updated code for ajp13 connector for tomcat 4. this version more or less works, but needs some major cleanup/refactoring. i ended up copying a bunch of code out of some files in the http connector package, and the Http*Base classes out of the connector package. perhaps some of this code could someday be put into utility/common classes... ajp.zip
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
You make a great job here and the ajp13 port to Tomcat 4.0 will be strategic for many sites. the code isn't real pretty right now. in fact, it's downright ugly! but that's ok, that's what refactoring is for ;) and hopefully, somebody who knows more can help! Refactoring could still be done later, but you show we could hope to see ajp13 in TC 4.0 and that's the important point. it's basically based on parts of the http connector, and Ajp13.java/Ajp13Interceptor.java from the 04.27 build of tomcat 3.3. i'm attaching a zip file containing my code. i've make it an ajp subpackage of org.apache.catalina.connector. I've started look at it. advice/help is welcome/wanted :) Keep up the good works. I'll test it against my mod_jk. Which version of Tomcat 4.0 must I use, TC 4.0B3 ? Regards
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core StandardContext.java
craigmcc01/04/30 14:55:09
Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
Log:
A load-on-startup servlet that throws ServletException or
UnavailableException from the init() method should *not* be fatal to the
entire application -- only to that servlet.
PR: Bugzilla #1557
Submitted by: Greg Murray [EMAIL PROTECTED]
Revision ChangesPath
1.56 +7 -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.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- StandardContext.java 2001/04/27 19:57:38 1.55
+++ StandardContext.java 2001/04/30 21:55:07 1.56
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.55 2001/04/27 19:57:38 remm Exp $
- * $Revision: 1.55 $
- * $Date: 2001/04/27 19:57:38 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.56 2001/04/30 21:55:07 craigmcc Exp $
+ * $Revision: 1.56 $
+ * $Date: 2001/04/30 21:55:07 $
*
*
*
@@ -141,7 +141,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.55 $ $Date: 2001/04/27 19:57:38 $
+ * @version $Revision: 1.56 $ $Date: 2001/04/30 21:55:07 $
*/
public class StandardContext
@@ -3250,7 +3250,9 @@
} catch (ServletException e) {
log(sm.getString(standardWrapper.loadException,
getName()), e);
-ok = false;
+// NOTE: load errors (including a servlet that throws
+// UnavailableException from tht init() method) are NOT
+// fatal to application startup
}
}
}
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
unfortunately, i have an immediate need for ajp13 in tomcat 4. i want to move to tomcat 4, but can't without connectivity between iis/netscape web servers and tomcat. porting ajp13 from tomcat 3.x to tomcat 4 seemed like it would be easier than writing iis/netscape connectors for the new webapp/warp stuff. especially since webapp seems to be a moving target AFAIK, IIS/Netscape connector only works with ajp12 not ajp13..at least this is the documented behavior and i have been unable to put it work with ajp13 ( i've tested on the last minutes ).. Saludos , Ignacio J. Ortega
cvs commit: jakarta-tomcat-4.0/tester/web/WEB-INF web.xml
craigmcc01/04/30 14:57:17
Modified:tester/src/bin tester.xml
tester/web/WEB-INF web.xml
Added: tester/src/tester/org/apache/tester ErrorPage07.java
Log:
Add a unit test to validate the load-on-startup servlet throws exception
from init() fix that was just committed.
Revision ChangesPath
1.36 +13 -0 jakarta-tomcat-4.0/tester/src/bin/tester.xml
Index: tester.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/tester/src/bin/tester.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- tester.xml2001/04/26 18:23:44 1.35
+++ tester.xml2001/04/30 21:57:14 1.36
@@ -264,6 +264,19 @@
status=200
outContent=ErrorPage06 PASSED - HTML/
+!-- == Load On Startup Exception Handling --
+
+!-- NOTE: HttpURLConnection throws FileNotFoundException on 503s --
+tester host=${host} port=${port} protocol=HTTP/1.0
+ request=${context.path}/ErrorPage07
+ debug=${debug}
+ status=503/
+
+tester host=${host} port=${port} protocol=HTTP/1.0
+ request=${context.path}/WrappedErrorPage07
+ debug=${debug}
+ status=503/
+
/target
1.1
jakarta-tomcat-4.0/tester/src/tester/org/apache/tester/ErrorPage07.java
Index: ErrorPage07.java
===
/* = *
* *
* The Apache Software License, Version 1.1 *
* *
* Copyright (c) 1999, 2000, 2001 The Apache Software Foundation. *
* All rights reserved.*
* *
* = *
* *
* Redistribution and use in source and binary forms, with or without modi- *
* fication, are permitted provided that the following conditions are met: *
* *
* 1. Redistributions of source code must retain the above copyright notice *
*notice, this list of conditions and the following disclaimer. *
* *
* 2. Redistributions in binary form must reproduce the above copyright *
*notice, this list of conditions and the following disclaimer in the *
*documentation and/or other materials provided with the distribution. *
* *
* 3. The end-user documentation included with the redistribution, if any, *
*must include the following acknowlegement: *
* *
* This product includes software developed by the Apache Software *
*Foundation http://www.apache.org/. *
* *
*Alternately, this acknowlegement may appear in the software itself, if *
*and wherever such third-party acknowlegements normally appear. *
* *
* 4. The names The Jakarta Project, Tomcat, and Apache Software *
*Foundation must not be used to endorse or promote products derived *
*from this software without prior written permission. For written *
*permission, please contact [EMAIL PROTECTED].*
* *
* 5. Products derived from this software may not be called Apache nor may *
*Apache appear in their names without prior written permission of the *
*Apache Software Foundation.*
* *
* THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES *
* INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY *
* AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL *
* THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY *
* DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL *
* DAMAGES (INCLUDING, BUT NOT LIMITED
Re: porting ajp13 to tomcat 4 (was Re: ajp13 question)
Keep up the good works. I'll test it against my mod_jk. Which version of Tomcat 4.0 must I use, TC 4.0B3 ? i'm using tc 4.0b3. as i keep updating my code, what is the best way to share it? keep posting updates to this list? -kevin.
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
unfortunately, i have an immediate need for ajp13 in tomcat 4. i want to move to tomcat 4, but can't without connectivity between iis/netscape web servers and tomcat. porting ajp13 from tomcat 3.x to tomcat 4 seemed like it would be easier than writing iis/netscape connectors for the new webapp/warp stuff. especially since webapp seems to be a moving target AFAIK, IIS/Netscape connector only works with ajp12 not ajp13..at least this is the documented behavior and i have been unable to put it work with ajp13 ( i've tested on the last minutes ).. What's the problem with ajp13 under IIS/NES ? I didn't have access to them but we may find help around...
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
The documentation is wrong...IIS works with ajp13...i'll change docs accordingly.. Saludos , Ignacio J. Ortega -Mensaje original- De: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Enviado el: martes 1 de mayo de 2001 0:04 Para: [EMAIL PROTECTED] Asunto: RE: porting ajp13 to tomcat 4 (was Re: ajp13 question) unfortunately, i have an immediate need for ajp13 in tomcat 4. i want to move to tomcat 4, but can't without connectivity between iis/netscape web servers and tomcat. porting ajp13 from tomcat 3.x to tomcat 4 seemed like it would be easier than writing iis/netscape connectors for the new webapp/warp stuff. especially since webapp seems to be a moving target AFAIK, IIS/Netscape connector only works with ajp12 not ajp13..at least this is the documented behavior and i have been unable to put it work with ajp13 ( i've tested on the last minutes ).. What's the problem with ajp13 under IIS/NES ? I didn't have access to them but we may find help around...
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
-Original Message- From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 01, 2001 12:10 AM To: '[EMAIL PROTECTED]' Subject: RE: porting ajp13 to tomcat 4 (was Re: ajp13 question) The documentation is wrong...IIS works with ajp13...i'll change docs accordingly.. Saludos , Ignacio J. Ortega Good. Did there is people around using NES/IPLANET which could confirm the status of ajp13 and NES ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 unfortunately, i have an immediate need for ajp13 in tomcat 4. i want to move to tomcat 4, but can't without connectivity between iis/netscape web servers and tomcat. porting ajp13 from tomcat 3.x to tomcat 4 seemed like it would be easier than writing iis/netscape connectors for the new webapp/warp stuff. especially since webapp seems to be a moving target AFAIK, IIS/Netscape connector only works with ajp12 not ajp13..at least this is the documented behavior and i have been unable to put it work with ajp13 ( i've tested on the last minutes ).. What's the problem with ajp13 under IIS/NES ? I didn't have access to them but we may find help around...
RE: tomcat crashes VM under NT
Title: RE: tomcat crashes VM under NT I'm using Tomcat 3.2.1 in NT with JVM 1.3.0, and it crashes with Dr. Watson error when I make jdbc-odbc connection to SQL server70 from my java servlet program. Does Tomcat have a bug here or I need to change some conf file?
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
Good. Did there is people around using NES/IPLANET which could confirm the status of ajp13 and NES ? I tested it ( long ago ), both NES and IIS ( yes, I did installed windows for that !). Ajp13 and JNI used to work fine ( JNI doesn't work very well with Apache1.3.x, as it's not multithreaded - but works just great on NES, IIS or Apache2.0 ). In fact, JNI is the tricky part, not ajp13. Costin
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
- HAve sense to continue naming ajp12 on IIS howto doc? i think not as there isnt a substitute for isape_redirect.dll as mod_jserver vs. mod_jk..so use ( or recommend ) a deprecated protocol has no sense for me .. ajp12 and ajp13 are both protocols used to link web-server to tomcat. when mod_jserv was designed only ajp12 exist. Later mod_jk added ajp13 and maintain ajp12 even it's clear that ajp13 is much more faster. If nobody complaints i will change *all* ajp12 references to ajp13..getting rid of every ajp12 reference ... +0
RE: Tomcat 3.2.2 beta 4
Costin, Let me know what you find and what the fix looks like. If its a simple fix then I'm OK with just developer testing and code review. Marc Just ship the damn thing Saegesser -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 5:37 PM To: [EMAIL PROTECTED] Subject: Re: Tomcat 3.2.2 beta 4 On Mon, 30 Apr 2001, Marc Saegesser wrote: Tomcat 3.2.2 beta 4 is available for download. If you can provide binaries for various please send them to me or update the FTP site. Thanks. Great !. Marc - one bad news, I have a bug that I think we should fix, it should be an easy fix and probably we don't need another beta for it ( I'm testing right now with beta4, maybe it's already there). The problem is related with virtual hosts - and tomcat hanging the threads when the host is not recognized. Hanging is bad - need to fix it. ( 3.3 doesn't have the problem ) Also, I'm not sure if case sensitive host is fixed in 3.2. Costin
RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
On Tue, 1 May 2001, Ignacio J. Ortega wrote: Good. Did there is people around using NES/IPLANET which could confirm the status of ajp13 and NES ? HAve sense to continue naming ajp12 on IIS howto doc? i think not as there isnt a substitute for isape_redirect.dll as mod_jserver vs. mod_jk..so use ( or recommend ) a deprecated protocol has no sense for me .. If nobody complaints i will change *all* ajp12 references to ajp13..getting rid of every ajp12 reference ... Well, I'm not sure. Ajp12 works fine, even if it's a bit slow. No development is going on - but the protocol is very stable, very well tested. We can recommend using ajp13, but I think we should keep the references to ajp12 - don't fix what works . Costin
Re: ANNOUNCE - web-connector
Hopefully we might even get back to one that worked as well as JServ's connector. As a goal, could you add back the ability to restart the JVM if necessary? Scott Sanders GOMEZ Henri wrote: A quick note to announce I'll start Thursday a mini-revolution in proposals/web-connector/ The goals of the revolution are: - improved ajp13: better configuration,etc - build improvements - support all tomcat versions - single codebase that will be used for all versions ( reduce maintainance overhead ) - add apr support - libtool and autoconf support - improved security and protocol negociation
[ANNOUNCEMENT] Tomcat 3.2.2 beta 4 released
I am pleased to announce that the Tomcat 3.2.2 beta 4 release is now available for download at http://jakarta.apache.org/builds/tomcat/release/v3.2.2-beta-4 Beta 4 fixes problems that could cause violations of the JSP specification for the JSP lifecycle methods, jspInit() and jspDestroy(), when the server is under high load and JSP source files are modified. The release notes file in src/doc/readme covers the details of the Tomcat 3.2.2 release. Marc A. Saegesser
[ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released
RPM available at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/rpms/ Linux i386 mod_jk.so (EAPI and STDAPI) at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/bin/li nux/i386/ - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
tomcat 4 http/1.1 connector and keep alives
why does the http/1.1 connector in tomcat 4 not set a connection: keep-alive header? doesn't it need to? thanks, -kevin
Re: tomcat 4 http/1.1 connector and keep alives
why does the http/1.1 connector in tomcat 4 not set a connection: keep-alive header? doesn't it need to? No. Keepalive is HTTP/1.0. In 1.1 connections are kept alive by default. Remy
cvs commit: jakarta-tomcat/proposals/jasper34/generator/org - New directory
costin 01/04/30 17:08:33 jakarta-tomcat/proposals/jasper34/generator/org - New directory
cvs commit: jakarta-tomcat/proposals/jasper34/generator/org/apache - New directory
costin 01/04/30 17:08:39 jakarta-tomcat/proposals/jasper34/generator/org/apache - New directory
cvs commit: jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/parser11 - New directory
costin 01/04/30 17:09:11 jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/parser11 - New directory
cvs commit: jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/core - New directory
costin 01/04/30 17:09:20 jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/core - New directory
cvs commit: jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/generator11/util - New directory
costin 01/04/30 17:09:32 jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/generator11/util - New directory
Re: ANNOUNCE - web-connector
on 4/30/01 4:00 PM, GOMEZ Henri [EMAIL PROTECTED] wrote: The goals of the revolution are: - improved ajp13: better configuration,etc - build improvements - support all tomcat versions - single codebase that will be used for all versions ( reduce maintainance overhead ) - add apr support - libtool and autoconf support - improved security and protocol negociation Could you also please add full Servlet API 2.3 support? We don't need another web connector that only half supports the latest servlet spec. thanks, -jon
