build error for coyote from JTC CVS against Tomcat 4.0.4 ;[

While trying to rebuild tomcat4 ajp stuff from latest JTC CVS, I got the following error, while trying to build against the TC 4.0.4 Buildfile: build.xml init: [echo] Coyote 1.0-dev prepare: static: report-tc4: [echo] Tomcat4 detected report-tc33: [echo

DO NOT REPLY [Bug 8099] - DefaultServlet looses query string information in redirect

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

>> Hum, I think the problem should be easier to detect (I hope so) > >Yeah, I agree. I actually think that my configuration could be screwed >somewhere, somehow (although I don't see how) because almost all Apache >2.0.x/Tomcat 3.3.x users would run into this kind of problem... Not sure. In fact

RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

On Wed, 2002-06-19 at 18:45, GOMEZ Henri wrote: > Hum, I think the problem should be easier to detect (I hope so) Yeah, I agree. I actually think that my configuration could be screwed somewhere, somehow (although I don't see how) because almost all Apache 2.0.x/Tomcat 3.3.x users would run into

RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

>Yes, pretty much. I'm guessing that Apache will try it's own page types >first (index.shtml, index.html etc.) and if if doesn't find any, pass >the request to Tomcat (through mod_jk) for index.jsp and then index.vm >(in that order, since that's how it's specified in DirectoryIndex). > >Just for t

RE: [Bug 6832] - Locale of the browser is ignored by the AJP13 connector

>I apologize. It is never fair to take out one's frustrations >on another. Ok, I could understand your language problem and I'll try to fix it. The problem is that TC 4.0.4 is out, and that patch may need a corrected tarball for connectors (and tomcat-ajp.jar) -- To unsubscribe, e-mail:

RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

Yes, pretty much. I'm guessing that Apache will try it's own page types first (index.shtml, index.html etc.) and if if doesn't find any, pass the request to Tomcat (through mod_jk) for index.jsp and then index.vm (in that order, since that's how it's specified in DirectoryIndex). Just for the rec

RE: [PATCH] When Session Max reached, throw out oldest session

It may be configurable, to allow both choices? André -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: 19 June 2002 10:26 To: Tomcat Developers List Subject: RE: [PATCH] When Session Max reached, throw out oldest session >Agreed... If we start invalidating sessions

RE: [PATCH] When Session Max reached, throw out oldest session

>Agreed... If we start invalidating sessions when too much memory is >"wasted", I'm going to choose a different servlet engine for >my 10m req/day >site... :) If I define that a session has a timeout, I want >that timeout to >be _real_ and if I run into memory problems, well, that's my >problem

RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

The question is : What should do http server ? forward to tomcat /index.jsp and if it fail, try next to forward /index.vm ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA

RE: [Bug 6832] / Hum need coyote here

Or the better way could be to copy CoyoteRequest code. But there will be 3 copy of Accept-Language decoding in TC 4.x, may be it should be placed elsewhere and useable by HttpProcessor, CoyoteRequest and AJP13 (may be tomcat-util ?) >>> >>>For Jk2, TC 4.x already is using a Coy

DO NOT REPLY [Bug 8099] - DefaultServlet looses query string information in redirect

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu