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
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
I'm just about to start the tag for Tomcat 3.2.2 beta 4.
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
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
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
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
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
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
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.
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
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
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
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
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.
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
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
-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
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?
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
-
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
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
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.
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
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
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]
why does the http/1.1 connector in tomcat 4 not set a connection:
keep-alive header? doesn't it need to?
thanks, -kevin
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
costin 01/04/30 17:08:33
jakarta-tomcat/proposals/jasper34/generator/org - New directory
costin 01/04/30 17:08:39
jakarta-tomcat/proposals/jasper34/generator/org/apache - New directory
costin 01/04/30 17:09:11
jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/parser11 - New
directory
costin 01/04/30 17:09:20
jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/core - New directory
costin 01/04/30 17:09:32
jakarta-tomcat/proposals/jasper34/generator/org/apache/jasper34/generator11/util -
New directory
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
34 matches
Mail list logo
