Hi,
*moan* Now I have to convert HTML tags we have that use request-time
attributes
into custom tags so that we can give them request time attributes. *sigh*
Is it going
to change in 1.3? I mean, XSLT allows all *non*-XSLT tags to have the
equivalent
of request-time attributes. I guess I
Hi Bojan,
you can use JavaMail for that. Below is a code snippet that extracts all the
parts of the form data (probably could need some cleanup though). I don't
know if this solution works under all circumstances, but we're using it
regularly with no problems so far.
Best regards
Andreas
If you liked that, also have a look at Spread:
http://www.spread.org/
The messaging engine (daemon) isn't written in Java, but it's very
fast and efficient, and runs on all the popular OSs. The Java clients
connect to it via TCP sockets, so the clients can be pure-Java. The
License is similar
cryptix, cryptix-asn1 and puretls RPMs are also in
the jpackage project:
http://www.jpackage.org
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F
AFAIK, Eric wanted to get to this at one point (and who could be better
qualified :). I think that it will be easier to do this in
Coyote than the
current Http11Connector.
+1, since Coyote may be the common http 1.1 connector for TC 3.3
and 4.0, let focus effort on it
--
To unsubscribe,
That was my first thought as well but I never carried it through, mostly
because I was too lazy to do the RTFM. I guess I can always rewrite my
own parser with the JavaMail stuff.
Thanks for the code...
Bojan
On Tue, 2002-03-12 at 19:54, Andreas Junghans wrote:
Hi Bojan,
you can use
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=7043.
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=7043.
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=7043.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I prefer not to move tomcat_util to J-T-C until after Tomcat 3.3.1,
which I plan on getting out this week or weekend at the latest.
After that, I'm +1.
Cheers,
Larry
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 11, 2002 7:10 PM
To: Tomcat
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=7026.
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=7052.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Thanks for the message. It is wonderful to know that we are not the only ones that got
stuck. In my opinion, JSP 1.2 XML has two bugs. This and the fact that we can't
specify that the output is really HTML in XHTML form. In other words, we need
something like the output method in XSLT and
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=7052.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Bill Barker [EMAIL PROTECTED] writes:
- Original Message -
From: Craig R. McClanahan [EMAIL PROTECTED]
By pluggable security implementations, I assume you really mean
pluggable SSL implementations? I'd certainly be +1 if someone wanted to
tackle porting the changes that were made
Nick Betteridge [EMAIL PROTECTED] writes:
I've written the TLS socket but haven't been able to get around to
testing it yet - swamped.
I know how that is.
The socket also has a certificate factory to enable certificates to be
read from a variety of sources.
This seems like a nice addition.
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=7052.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi All,
I've been installed tomcat 4.0.3 for windows successfully. But, now when i
try to install tomcat 4.0.3 in AIX, i can start the Tomcat ... but
with some error message. I've tried to debug it, but still i can't find why
it happens.
It's seemed from the error message, the Tomcat can't
Coyote 1.0 Beta 2 is now available, and includes:
- A high performance HTTP/1.1 processor
- An adapter for Tomcat 3.3.x (new in this release)
- An adapter for Tomcat 4.0.x
- Bugfixes over 1.0 Beta 1
Binaries can be downloaded at:
[EMAIL PROTECTED] wrote:
On Tue, 12 Mar 2002, jean-frederic clere wrote:
What to do when myvhost is www.apache.org for example...
uri.www.apache.org:/examples.worker? Using ':' instead of '.' does not
solve the problem.
Sounds good.
If we use a hierarchical name we also solve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 12, 2002 11:01 AM
To: Tomcat Developers List
Subject: RE: cvs commit:
jakarta-tomcat-connectors/util/java/org/apache/to
mcat/util/http MimeHeaders.java
On Tue, 12 Mar 2002, Larry
Hi,
I've discovered something that looks like a bug to me, although I'm not
sure whethter this should/can be classified as a bug. The following
behavour occurs when you put % %-JSP tags inside a java comment in a
JSP file. The code following the comment will be displayed on the page
when
On Tue, 12 Mar 2002, jean-frederic clere wrote:
myworker1=
Would be the same as:
myworker1=ajp13://localhost:8009?lbfactor=0debug=ERROR
(no load balancing and only log error messages).
How to describe AF_UNIX or shared memory (as transport but not protocol)?
costin 02/03/12 11:11:36
Removed: jk/native/nt_service nt_service.dsp
Log:
Removed to be added back as -kb
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
costin 02/03/12 11:12:18
Added: jk/native/nt_service nt_service.dsp
Log:
Added as binary, with dos file ending.
Revision ChangesPath
1.8 +199 -199 jakarta-tomcat-connectors/jk/native/nt_service/nt_service.dsp
--
To unsubscribe, e-mail:
on 3/11/02 10:08 PM, Bojan Smojver [EMAIL PROTECTED] wrote:
I was looking for a class capable of parsing the above, but I couldn't
find one in Jakarta source tree (in the meantime I whacked a dodgy one
together, so my immediate problem is solved). Can someone point me to
the 'proper' one in
on 3/12/02 1:08 AM, GOMEZ Henri [EMAIL PROTECTED] wrote:
We speak about spread some times ago but the licence wasn't Apache
at this time, and yes it's another good Broadcast system.
Good point it support native and java.
Spread has a BSD license now. Thanks to many ASF members speaking to
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=7059.
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=7059.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm02/03/12 12:20:39
Modified:catalina/src/share/org/apache/catalina/connector Tag:
tomcat_40_branch HttpResponseBase.java
Log:
- Revert the patch for 6600, which was causing URL encoding to fail.
- Bug 6600 will be converted to an enhancement request
remm02/03/12 12:20:49
Modified:catalina/src/share/org/apache/catalina/connector
HttpResponseBase.java
Log:
- Revert the patch for 6600, which was causing URL encoding to fail.
- Bug 6600 will be converted to an enhancement request (the spec doesn't
remm02/03/12 12:21:22
Modified:coyote/src/java/org/apache/coyote/tomcat4
CoyoteResponse.java
Log:
- Port change from the HTTP connector.
- Revert the patch for 6600, which was causing URL encoding to fail.
- Bug 6600 will be converted to an
Attached is a patch to the jtc jk_nt_service.c to allow service properties
to be supplied as arguments on the command line when the service is
installed.
Most of this is a merge from the tomcat 3.3 tree, with the addition of
allowing the
service description to be set.
--
tim
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=7059.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I prefer not to move tomcat_util to J-T-C until after Tomcat 3.3.1,
which I plan on getting out this week or weekend at the latest.
After that, I'm +1.
Agree
What about including the alpha of coyote and jk2(java) with 3.3.1 ?
( disabled, but easy to activate )
+1, disabled by default but
I have implemented the mod_jk (1.2) request logging I proposed
a few weeks
ago. Its up and running.
/*
* JkRequestLogFormat Directive Handling
*
* JkRequestLogFormat format string
*
* %b - Bytes sent, excluding HTTP headers. In CLF format
* %B - Bytes sent, excluding HTTP headers.
* %H
Even more extreme - use full uri, with query strings. We're in a http
server, we should know how to parse this kind of stuff :-)
Location /examples
JkUriSet worker
ajp13://tomcat_host.my.com:8009?lbfactor=10debug=INFO
/Location
Good, but Apache oriented
And another idea for
I hope that the following server.xml snip correctly describes the
inclusion!
Our experience with 3.3 was that just having a single socket factory
didn't work very well, because you also need to choose the right
classes to get socket info... The 3.3 approach was to have a
single meta-class
We speak about spread some times ago but the licence wasn't Apache
at this time, and yes it's another good Broadcast system.
Good point it support native and java.
Spread has a BSD license now. Thanks to many ASF members
speaking to the
spread developers and convincing them to switch.
craigmcc02/03/12 13:14:16
Modified:catalina/src/share/org/apache/catalina/servlets
LocalStrings.properties ManagerServlet.java
webapps/tomcat-docs manager-howto.xml
Added: catalina/src/share/org/apache/catalina/ant
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=7061.
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=6600.
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=7061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Tue, 12 Mar 2002, GOMEZ Henri wrote:
Another log level of request was added also. If log level
is = request
and JkRequestLogFormat is configured, requests will be logged.
If JkLogLevel = REQUEST ?
Please, no more levels... Debug, info, error, etc is enough - request is
not a level
If JkLogLevel = REQUEST ?
Please, no more levels... Debug, info, error, etc is enough -
request is
not a level but a channel/log/whatever.
What next, add a 'headers' level to display the headers ? Is
headersrequest ?
Good idea the dump of header, I'll often have to track problems
with
Has anyone successfully got Tomcat 4 running under Unix System Services on
an OS390 mainframe machine?
Thanks,
Stephen J. Guthrie
Regional Sales Manager
Mantissa Corporation
2200 Valleydale Road
Birmingham, AL 35244
(800) 438-7367
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For
GOMEZ Henri wrote:
I have implemented the mod_jk (1.2) request logging I proposed
a few weeks
ago. Its up and running.
/*
* JkRequestLogFormat Directive Handling
*
* JkRequestLogFormat format string
*
* %b - Bytes sent, excluding HTTP headers. In CLF format
* %B - Bytes sent, excluding HTTP
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=7059.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
GOMEZ Henri wrote:
If JkLogLevel = REQUEST ?
Please, no more levels... Debug, info, error, etc is enough -
request is
not a level but a channel/log/whatever.
What next, add a 'headers' level to display the headers ? Is
headersrequest ?
Good idea the dump of header, I'll often have to
On Tue, 12 Mar 2002, Glenn Nielsen wrote:
worker.ajp13.logRequest=%b %w
The new JkRequestLogFormat scopes at the Apache VirtualHost,
so you can specifiy different request logging formats for
different virtual hosts. The above wouldn't allow that.
You're right, but will work with
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=7059.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
craigmcc02/03/12 17:26:49
Modified:catalina/src/share/org/apache/catalina/core
StandardHostDeployer.java
catalina/src/share/org/apache/catalina/loader
StandardClassLoader.java
remm02/03/12 18:25:14
Modified:.Tag: tomcat_40_branch RELEASE-NOTES-4.0.4-B2.txt
Log:
- Changelog update.
Revision ChangesPath
No revision
No revision
1.1.2.2 +4 -1
There are many ways to take advantage of Coyote in Tomcat 4, but I'd like to
start with some limited changes at first. Most of these proposed changes are
Coyote-related (hence the subject of the message), and all involve some
refactoring / API additions.
A) URI decoding refactoring. To avoid
+1 for everything
Costin
On Tue, 12 Mar 2002, Remy Maucherat wrote:
There are many ways to take advantage of Coyote in Tomcat 4, but I'd like to
start with some limited changes at first. Most of these proposed changes are
Coyote-related (hence the subject of the message), and all involve
larryi 02/03/12 19:40:07
Modified:src/etc/jk wrapper.properties
Log:
Added quotes around wrapper.javabin in the wrapper.cmd_line.
Submitted by: David Schreibman
Added wrapper.jvm.options and some documentation.
Revision ChangesPath
1.4 +24 -4
larryi 02/03/12 19:43:33
Modified:src/share/org/apache/tomcat/modules/server
PoolTcpConnector.java
Log:
Remove setting the socketFactory attributes from checkSocketFactory().
It is now handled in engineInit() where it should have been in the first
larryi 02/03/12 19:44:36
Modified:src/share/org/apache/jasper JspC.java
Log:
Port a couple of fixes from Tomcat 4.x.
Revision ChangesPath
1.25 +2 -1 jakarta-tomcat/src/share/org/apache/jasper/JspC.java
Index: JspC.java
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=7037.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Tue, 12 Mar 2002, Glenn Nielsen wrote:
Why? This is a minor change that IMO fixes a problem.
The example JkMount /servlet/* doesn't work with Tomcat. There needed to be
a way to easily configure passing of servlet requests to Tomcat without having
to configure it for each Context Path.
craigmcc02/03/12 20:13:34
Modified:webapps/tomcat-docs jndi-resources-howto.xml
Log:
Update JNDI documentation to reflect the switch from Tyrex to DBCP for default
connection pool support.
Revision ChangesPath
1.12 +5 -28
on 3/12/02 6:30 PM, Remy Maucherat [EMAIL PROTECTED] wrote:
A) URI decoding refactoring. To avoid doing some URI decoding in many places
in the pipeline, a decodedURI field (with associated getter/setter) should
be added in the HttpRequest interface, and used in the Catalina pipeline.
This
The priority is emerg,warning,request,info,debug.
Your though is that someone might want just request loggin without
emerg and warning?
Yep, you could even have this kind of log in a separate log file
for statistic, that's what is used for example by mod_gzip.
Very very usefull when you want to
on 3/12/02 6:30 PM, Remy Maucherat [EMAIL PROTECTED] wrote:
A) URI decoding refactoring. To avoid doing some URI decoding in many
places
in the pipeline, a decodedURI field (with associated getter/setter)
should
be added in the HttpRequest interface, and used in the Catalina
pipeline.
I'm ok with dropping request from the JkLogLevel, though I wish
someone had said something when I first proposed this. :-)
No the idea is excellent, but it will be more usefull to get this
feature in a separate logfile (httpd use error, access) as does
mod_gzip.
--
To unsubscribe, e-mail:
+1, share code, share code.
I'll be +1 to have it also in 3.3.2
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
-Original
You're right it's better :
worker.ajp13.logRequest={The Proposed JkRequestLogFormat}
ie
worker.ajp13.logRequest=%b %w
The new JkRequestLogFormat scopes at the Apache VirtualHost,
so you can specifiy different request logging formats for
different virtual hosts. The above
On Wed, 13 Mar 2002, GOMEZ Henri wrote:
+1, share code, share code.
I'll be +1 to have it also in 3.3.2
'decodedRequest' is already there, commons-logging is trivial to
add. The lifecycle of modules is also fine, the only problem is the
ordering of modules - but so far it is under
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Tuesday, March 12, 2002 9:26 PM
Subject: Re: [PROPOSAL] Proposed integration of Coyote in 4.0-HEAD
on 3/12/02 6:30 PM, Remy Maucherat [EMAIL PROTECTED] wrote:
A) URI
Disclaimer:
A +1 vote below does not necessarily mean that I'm going to pledge ongoing
support to o.a.c.tomcat4 (although it is very well done, and I relied
heavily on it for developing o.a.c.tomcat3). However, I do plan to support
o.a.c and o.a.c.http11.
- Original Message -
From: Remy
A) URI decoding refactoring. To avoid doing some URI decoding in many
places
in the pipeline, a decodedURI field (with associated getter/setter)
should
be added in the HttpRequest interface, and used in the Catalina
pipeline.
This also has the advantage to guarantee that no double URI
remm02/03/12 23:42:11
Modified:coyote/src/java/org/apache/coyote/tomcat4
CoyoteConnector.java CoyoteProcessor.java
Log:
- Add the URI normalization code from TC 4 used to protect against some URI
encoding based attacks. This may be useless in the
Remy Maucherat wrote:
There are many ways to take advantage of Coyote in Tomcat 4, but I'd like to
start with some limited changes at first. Most of these proposed changes are
Coyote-related (hence the subject of the message), and all involve some
refactoring / API additions.
A) URI
73 matches
Mail list logo
