DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31594.
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://issues.apache.org/bugzilla/show_bug.cgi?id=31590.
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://issues.apache.org/bugzilla/show_bug.cgi?id=31590.
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://issues.apache.org/bugzilla/show_bug.cgi?id=31592.
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://issues.apache.org/bugzilla/show_bug.cgi?id=31590.
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://issues.apache.org/bugzilla/show_bug.cgi?id=31590.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
mturk 2004/10/08 00:19:34
Modified:jk/native/common jk_uri_worker_map.c
Log:
Untabify the source.
Revision ChangesPath
1.22 +58 -59jakarta-tomcat-connectors/jk/native/common/jk_uri_worker_map.c
Index: jk_uri_worker_map.c
mturk 2004/10/08 00:20:33
Modified:jk/native/common jk_util.c
Log:
Untabify the source and use size_t for strlens.
Revision ChangesPath
1.29 +26 -26jakarta-tomcat-connectors/jk/native/common/jk_util.c
Index: jk_util.c
mturk 2004/10/08 00:22:58
Modified:jk/native/common jk_md5.c
Log:
Untabify the source code
Revision ChangesPath
1.10 +119 -135 jakarta-tomcat-connectors/jk/native/common/jk_md5.c
Index: jk_md5.c
mturk 2004/10/08 00:23:51
Modified:jk/native/common jk_md5.h
Log:
Int is not 32 bits on all platforms.
Revision ChangesPath
1.3 +12 -4 jakarta-tomcat-connectors/jk/native/common/jk_md5.h
Index: jk_md5.h
mturk 2004/10/08 00:18:04
Modified:jk/native/common jk_ajp14_worker.c
Log:
Comment the login service for now.
Revision ChangesPath
1.20 +4 -1 jakarta-tomcat-connectors/jk/native/common/jk_ajp14_worker.c
Index: jk_ajp14_worker.c
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31590.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
mturk 2004/10/08 00:34:44
Added: jk/native/common .indent.pro
Log:
Indent file for mod_jk.
Revision ChangesPath
1.1 jakarta-tomcat-connectors/jk/native/common/.indent.pro
Index: .indent.pro
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31590.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Attention:
A Spyware or virus was found in an Email message you sent.
This Email scanner intercepted it and stopped the entire message
reaching its destination.
Please update your Spyware or virus scanner or contact your IT support
personnel as soon as possible as you have a virus or Spyware
mturk 2004/10/08 00:50:41
Modified:jk/native/common jk_ajp12_worker.c jk_ajp13.c
jk_ajp13_worker.c jk_ajp14.c jk_ajp14_worker.c
jk_ajp_common.c jk_connect.c jk_context.c
jk_jni_worker.c jk_lb_worker.c jk_map.c
Hi to all,
Did there is plan to add unix-socket support in ajp_proxy ?
Some people seems to use JK2 for the quick unix-socket and wonder if
they could use them in mod_proxy/ajp_proxy.
BTW, since ajp_proxy is 100% APR it should be easier ?
Regards
mturk 2004/10/08 01:55:14
Modified:jk/native/apache-1.3 mod_jk.c
jk/native/apache-2.0 mod_jk.c
jk/native/domino dsapifilter.h inifile.c inifile.h
jk_dsapi_plugin.c
jk/native/iis jk_isapi_plugin.c
-Mensaje original-
De: jean-frederic clere [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 08 de octubre de 2004 8:28
Para: Jesús Luna
Asunto: Re: Problems with SSL_CLIENT_CERT_CHAIN_n from servlet
I have not (yet) got it working but the idea to have more httpd variables
available
Henri Gomez wrote:
Hi to all,
Did there is plan to add unix-socket support in ajp_proxy ?
Some people seems to use JK2 for the quick unix-socket and wonder if
they could use them in mod_proxy/ajp_proxy.
BTW, since ajp_proxy is 100% APR it should be easier ?
Think that APR doesn't support AF_UNIX.
remm2004/10/08 02:34:02
Modified:catalina/src/share/org/apache/catalina/core
NamingContextListener.java LocalStrings.properties
Log:
- Register datasource with JMX.
- With DBCP, this is enough to provide JMX management and monitoring. It might work
mturk 2004/10/08 03:37:12
Modified:jk/native/iis jk_isapi_plugin.c
Log:
Remove computing properties file on each dll event.
Fix reporting error page to client, and few compile time warnigs.
Revision ChangesPath
1.25 +43 -38
mturk 2004/10/08 04:08:47
Modified:jk/native CHANGES.txt
Log:
Recent changes to jk.
Revision ChangesPath
1.22 +7 -1 jakarta-tomcat-connectors/jk/native/CHANGES.txt
Index: CHANGES.txt
===
Hi,
Here is my Todo List for JK:
- Documentation
- Use Apache coding style (already done 90%) using simple .indent.pro
- Fix all 64/32 bit compatibility issues.
- Backport IIS Worker thread pool from JK2.
- Backport some ajp messaging stuff from proxy_ajp (mostly performance).
- Backport shared
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26523.
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://issues.apache.org/bugzilla/show_bug.cgi?id=31581.
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://issues.apache.org/bugzilla/show_bug.cgi?id=31581.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
+1, will help as much as possible
On Fri, 08 Oct 2004 13:28:49 +0200, Mladen Turk [EMAIL PROTECTED] wrote:
Hi,
Here is my Todo List for JK:
- Documentation
- Use Apache coding style (already done 90%) using simple .indent.pro
- Fix all 64/32 bit compatibility issues.
- Backport IIS
May be we could ask us to work on this ?
porting them from jk2 to jk is a good idea
On Fri, 08 Oct 2004 11:06:08 +0200, Mladen Turk [EMAIL PROTECTED] wrote:
Henri Gomez wrote:
Hi to all,
Did there is plan to add unix-socket support in ajp_proxy ?
Some people seems to use JK2 for the
Mladen Turk wrote:
Hi,
Here is my Todo List for JK:
- Documentation
- Use Apache coding style (already done 90%) using simple .indent.pro
- Fix all 64/32 bit compatibility issues.
- Backport IIS Worker thread pool from JK2.
- Backport some ajp messaging stuff from proxy_ajp (mostly performance).
-
Remy Maucherat wrote:
- Backport JNI from JK2 with lots improvements.
I still don't see benefits in JNI as a transport for JK. Only trouble
(no matter how I look at it, it seems like it would actually make the
whole system much less robust) and complexity.
Did I miss something ?
The JNI was
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31473.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Yes, it is a known problem that using the AJP/1.3 Connector isn't
spec-complient. The Ajp13 protocol is still stuck at Servlet v2.2, and only
exposes one cert.
- Original Message -
From: Jesús Luna [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Tomcat Developers List [EMAIL PROTECTED]
Remy Maucherat wrote:
- Backport JNI from JK2 with lots improvements.
I still don't see benefits in JNI as a transport for JK. Only trouble
(no matter how I look at it, it seems like it would actually make the
whole system much less robust) and complexity.
Did I miss something ?
I have to agree
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29521.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Over all, I don't, personally, think that it's worth trying to build on the
existing Jk code base. However, if you have an itch
- Original Message -
From: Mladen Turk [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Friday, October 08, 2004 4:28 AM
Subject: JK
Bill Barker wrote:
Over all, I don't, personally, think that it's worth trying to build on
the existing Jk code base. However, if you have an itch
Well, we deceased JK2, for Apache2.1 we have proxy_ajp.
Until Apache2.1 becomes the only server around the net,
I'll stick with JK for all those
[EMAIL PROTECTED] wrote:
remm2004/10/08 02:34:02
Modified:catalina/src/share/org/apache/catalina/core
NamingContextListener.java LocalStrings.properties
Log:
- Register datasource with JMX.
- With DBCP, this is enough to provide JMX management and monitoring.
Mladen Turk wrote:
Bill Barker wrote:
Over all, I don't, personally, think that it's worth trying to build
on the existing Jk code base. However, if you have an itch
Well, we deceased JK2, for Apache2.1 we have proxy_ajp.
Until Apache2.1 becomes the only server around the net,
I'll stick
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31439.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Remy Maucherat wrote:
Over all, I don't, personally, think that it's worth trying to build
on the existing Jk code base. However, if you have an itch
Well, we deceased JK2, for Apache2.1 we have proxy_ajp.
Until Apache2.1 becomes the only server around the net,
I'll stick with JK for all
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project jakarta-tomcat-catalina has an issue affecting its community integration.
This issue
From: Keith Wannamaker [EMAIL PROTECTED]
Ballot
[ ] Alpha
[ ] Beta
[X] Stable
/Ballot
I tested connector bugs 20184 24763 are fixed with this
release. All the major branches have this fix now (3.x 4.1 and
5.x). I'm now aware that this release passes all the watchdog
tests, too.
-Kurt
Where can I find test cases I can use to verify that my changes to the Coyote
Connector haven't broken anything?
I work for Unisys corporation, and we are modifying the Coyote Connector to integrate
Tomcat 5.0.28 with our native HTTP server on MCP systems (mainframe systems with
origins in the
From: Mladen Turk [EMAIL PROTECTED]
Remy Maucherat wrote:
Over all, I don't, personally, think that it's worth trying to build
on the existing Jk code base. However, if you have an itch
Well, we deceased JK2, for Apache2.1 we have proxy_ajp.
Until Apache2.1 becomes the only server
Hey Keith,
Hey Amy, would you mind running the TCKs against the 4.1.31 rc?
http://apache.org/~keith/rc2/
How does one go about obtaining these tests?
I only have the TCKs for the latest specs Servlet 2.4/JSP2.0 so it won't be
compatible with Tomcat 4.1.
I believe Apache has contacts that have
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30774.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
47 matches
Mail list logo
