DO NOT REPLY [Bug 8087] New: - HttpSessionAttributeListener.attributeRemoved() not working with URLRewriting

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

[PATCH] Small fix for StandardServer ctr

o.a.c.core.StandardServer's ctr calls super(), but the class does not extend anything. The call is legal, but misleading. The following patch removes it. The patch is against HEAD, but it's also an issue in 4.0.x. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia

cvs commit: jakarta-tomcat gump.xml

larryi 02/04/14 21:28:07 Modified:.gump.xml Log: Remove commons-logging dependency. Update to the target which builds jakarta-tomcat with only the jakarta-tomcat-connectors util dependency, which won't rebuild if already built. Revision ChangesPath 1.3

cvs commit: jakarta-tomcat build.xml

larryi 02/04/14 21:25:24 Modified:.build.xml Log: Note sure if this will be in time for tonight's Gump build. The tomcat-jar target still included the coyote target, which would cause it to fail. This also implements a different approach to keeping Gump happy. Rath

cvs commit: jakarta-tomcat-connectors/util build.xml

larryi 02/04/14 21:07:01 Modified:util build.xml Log: Include in util/build/lib a copy of the actual commons-logging.jar used in the build. Allows the choice of the logging jar to remain local, and an external project can get this choice from a known location. Revisio

Tomcat 4 target JDK is 1.2? but ShutdownHook is 1.3?

cvs HEAD o.a.c.startup.Catalina has a Runtime.addShutdownHook() call, but ShutdownHooks are a 1.3 thing. I was assuming (based on the website docs) that 4.1 was supposed to be JDK 1.2+. Is that incorrect? Is JDK 1.3 the target? In an amusing (and perhaps useless) twist, MinTC (embeddable serv

DO NOT REPLY [Bug 8079] New: - Tomcat cannot start if appBase directory is accessable but not readable.

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

DO NOT REPLY [Bug 8075] - Parameter parsing fails when the value has an '=' character in it

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

DO NOT REPLY [Bug 8075] New: - Parameter parsing fails when the value has an '=' character in it

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: Corrupted Ouput - Tomcat 4.0.3

> Remy Maucherat wrote: > > > > > There seems to be a bug in the servlet output. > > > > Tomcat 4 does not corrupt images, binaries, or anything like that. This has > > been proven on and on by many people using it (like myself) on various > > websites. > > > > That logic doesn't work. The fact t

Re: Corrupted Ouput - Tomcat 4.0.3

Remy Maucherat wrote: > > > There seems to be a bug in the servlet output. > > Tomcat 4 does not corrupt images, binaries, or anything like that. This has > been proven on and on by many people using it (like myself) on various > websites. > That logic doesn't work. The fact that it works for s

Bug report for Tomcat 4 [2002/04/14]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 3 [2002/04/14]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

cvs commit: jakarta-tomcat build.xml gump.xml

costin 02/04/14 09:04:52 Modified:.build.xml gump.xml Log: Hopefully this will fix next gump. Revision ChangesPath 1.174 +28 -12jakarta-tomcat/build.xml Index: build.xml === RCS fil

RE : Corrupted Ouput - Tomcat 4.0.3

I guess you are right. I do not think Tomcat is responsible for this. I suspect that the reason v3 appears to be fine could be due to a different output buffer size. I may try to play with this to prove myself that the problem is in my network (clues on how to change output buffer size on V3 and

[GUMP] Build Failure - Tomcat 3.x

This email is autogenerated from the output from: Buildfile: build.xml detect: msg.jdk12: [echo] Detected JDK1.2

Re: Corrupted Ouput - Tomcat 4.0.3

> There seems to be a bug in the servlet output. I installed two versions > of Tomcat freshly installed on my machine. All I did was change the port > numbers and add 2 image files: > > Tomcat 3.2.4: http://24.202.111.74:8081/test.jpg > Tomcat 4.0.3: http://24.202.111.74:8082/test.jpg Tomcat