Henri Gomez wrote:
Hi to all,
I would like to propose you a new tomcat commiter, Kurt Miller
which as proposed many usefull patches for JK2
Since we want to deprecated jk and focus jk2, we need
more people involved on jk2.
Vote please.
+1
Bill Barker wrote:
Hi,
Tomcat 5.0 always adds a charset=ISO-8859-1 to the content type. While
this is I think relatively legal, it is rather risky (it causes problems
with some clients, as I've read on tomcat-user), and very dubious when
dealing with non text data.
Example:
GET /tomcat.gif
Hi,
As was discussed earlier, I'll put in a new tag when the final
specifications are available.
There may not be a need for a new beta release since:
- 5.0.14 has been rather successful
- an extra beta testing month has been added
- the CVS code has been rather stable for a while
Of course,
Is tomcat 5 going to suport tag file pooling as well as tag pooling.
When looking at some generated code I notice that it was currently only
pooling tags not tag files?
Thanks,
john
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
The JSP 2.0 specification states that these must not be cached.
See section 7.1.5.
On Wed, 2003-11-12 at 10:48, jakarta wrote:
Is tomcat 5 going to suport tag file pooling as well as tag pooling.
When looking at some generated code I notice that it was currently only
pooling tags not tag
Kurt Miller a écrit :
From: Glenn Nielsen [EMAIL PROTECTED]
Perhaps the mod_jk connector should not be released with Tomcat 4/5 since
it
has its own release cycle and we are already doing separate releases of
these.
Regards,
Glenn
Would this work...
When a stable version of mod_jk or
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=24650.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hello,
I hate to post this to the dev list, but we need consulting help. I
have no idea where to look for reputable Tomcat consulting.
We are at our wits end and ready to make the jump to commercial
software due to a signal 11 crashing problem with our Tomcat servers.
We have found about a
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=24655.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=24655.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
From: Henri Gomez [EMAIL PROTECTED]
Kurt Miller a écrit :
From: Glenn Nielsen [EMAIL PROTECTED]
Perhaps the mod_jk connector should not be released with Tomcat 4/5
since
it
has its own release cycle and we are already doing separate releases of
these.
Regards,
Glenn
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=24655.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Does anyone know what the contents of workers.properties should look
like for JK2? I'm producing a new version of the Domino redirector based
on the ISAPI one but I can't find a sample workers.properties for the
ISAPI filter.
From stepping through the filter's initialisation code it's clear
Andy Armstrong wrote:
Does anyone know what the contents of workers.properties should look
like for JK2? I'm producing a new version of the Domino redirector based
on the ISAPI one but I can't find a sample workers.properties for the
ISAPI filter.
From stepping through the filter's
Kurt Miller wrote:
From: Henri Gomez [EMAIL PROTECTED]
Kurt Miller a écrit :
From: Glenn Nielsen [EMAIL PROTECTED]
Perhaps the mod_jk connector should not be released with Tomcat 4/5
since
it
has its own release cycle and we are already doing separate releases of
these.
Regards,
Glenn
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=24660.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=24660.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Remy,
From: Remy Maucherat [EMAIL PROTECTED]
Subject: [5.0] content-type and charset issues
Date: Tue, 11 Nov 2003 16:10:24 +0100
Message-ID: [EMAIL PROTECTED]
Tomcat 5.0 always adds a charset=ISO-8859-1 to the content type. While
this is I think relatively legal, it is rather risky (it causes
18 matches
Mail list logo
