I was thinking of moving it to Http10Interceptor.getInfo, but otherwise that
was more or less what I was thinking.
- Original Message -
From: jean-frederic clere [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Friday, November 16, 2001 3:10 AM
Subject: Re: Portable
- Original Message -
From: Eric Rescorla [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, November 14, 2001 9:17 AM
Subject: Re: Portable SSL Support
jean-frederic clere [EMAIL PROTECTED] writes:
Eric Rescorla wrote:
A few
I was originally leaning towards 2a, but Costin has convinced me of the
merits of 2b+1. It is simplest and more generalizable to Ajp14/JNI in
j-t-c. It also allows you to skip implementing the pooling/recycling stuff
(since it should be possible to reuse one instance per connector).
If you
For what it's worth (since I can't vote), I agree with Jon. TC3.3 hasn't
had a long enough beta cycle yet to push through an RC cycle this fast. As
it is, I'm going to be lucky to have time to install RC1 before RC2 comes
out. Keeping up with 4.0 isn't a good enough reason, since I'm sure that
Using:
Apache 1.3.17
TC3.3 B1
Ajp13
Java 1.3.1
making the request http://myserver/%3f%41%3d%42.jsp was interpreted as a
request for the file /?A=B.jsp. JspInterceptor then happily creates a
page containing the contents of the ROOT directory. The attached patch
forbids such silliness.
This is only a cosmetic patch, so it may not make the cut for TC3.3, but
the diff is against TC3.3B1. At the moment, when the user hits the stop
button, it shows up in the Apache logs with a status code of 500 (regardless
of the status code returned by Tomcat). With this patch, the Apache
The configuration:
ApacheConfig forwardAll=false useJkMount=true
jkDebug=error noRoot=false /
causes ApacheConfig to output a line of the form:
Alias / /path/to/ROOT
which makes Apache very unhappy when trying to find static files.
One alternative to the attached
This fixes the problem reported by Angel Aray in thread 23795. The diff is
against TC3.3 M4. What was happening is that the user hitting the stop
button in the browser was invoking the re-try broken connection logic. This
totally freaks out the proxy server who now thinks that the re-sent page
I don't really expect this to be approved for inclusion, since it relies
on ApacheConfig having too much knowledge about Context internals. I'm
submitting it primarily to demonstrate to the ajp14/warp crowd that it is
possible to auto-generate mappings short of JkMount /my-app/* ajp13.
The bufferSize variable in BodyContentImpl is declared as an int. This
results in an integer overflow very quickly for even moderately big output.
(Think displaying the results of a SQL table as a HTML table). I imagine
that the ultimate solution will be to declare it as a long, but in the mean
My reading of the spec is that after calling Tag.release, the tag handler
could be safely put back into the pool. However calling Tag.release after
doEndTag isn't mandatory. If the compiler is smart enough, it may re-use a
tag without releasing it first if the second invocation uses a super-set
Title: Re: TC3.3m1 Possible bug with session.invalidate
The place to look is
src/share/org/apache/tomcat/modules/session/SimpleSessionStore.java. Or,
better, get the latest version of this file since the bug was fixed about two
weeks ago.
- Original Message -
From:
Dunlop,
JkWorkersFiles is the main problem inside of a VirtualHost. I don't know
about JkLogFile. JkMount is legal inside of a VirtualHost.
- Original Message -
From: "Stephen Jones" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, February 28, 2001
It was getting to be too much work to keep my web.xml files synced with
httpd.conf, so I got ApacheConfig.java to do it for me. The following is
for Tomcat 3.3M1:
*** ApacheConfig.java.orig Thu Mar 1 16:40:46 2001
--- ApacheConfig.java Thu Mar 1 16:38:26 2001
***
*** 328,337
It has more to do with a bug in SimpleSessionStore.java. It recycles the
session on create, so then the instance is re-used for the next new session.
I've patched it via:
*** SimpleSessionStore.java.origMon Feb 26 14:59:53 2001
--- SimpleSessionStore.java Wed Feb 28 09:36:40 2001
When a JSP file is specified via a servlet-mapping in the web.xml file,
tomcat tries to compile the mapping rather than the JSP file.
*** JspInterceptor.java.origTue Feb 27 18:58:50 2001
--- JspInterceptor.java Tue Feb 27 18:59:10 2001
***
*** 585,590
--- 585,591
This is a very nice feature. Just for cleanliness, you might want to remove
the "tomcat.cp" property logic at line #426.
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 26, 2001 1:42 AM
Subject: cvs commit:
It seems that the only way to add files to the CLASSPATH in 3.3 is via
the tomcat.cp property, but it doesn't seem to be working quite right.
Below is the patch to org/apache/tomcat/startup/Main.java that works for me.
133,134c133,134
if( ! base.endsWith( "/" ) )
18 matches
Mail list logo