[PROPOSAL] Add Post to the clear list for protected pages

At the moment (with the default settings), Tomcat 4.1.x and higher add HTTP headers to non-SSL protected pages to prevent intermediate proxies from caching them. According to the HTTP/1.1 RFC (and even the HTTP/1.0 RFC), POSTed pages are not allowed to be cached by proxies (for the obvious reasons

DO NOT REPLY [Bug 21620] - org.apache.catalina.loader.Reloader missing from catalina.jar

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

cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup Embedded.java

luehe 2003/07/15 17:18:11 Modified:catalina/src/share/org/apache/catalina/startup Embedded.java Log: - Added Embedded.createConnector() methods that take address of type String (instead of java.net.InetAddress), since the InetAddress is always converted to a string (and sto

DO NOT REPLY [Bug 21621] New: - enableLookups in default server.xml defaults to true

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 21620] New: - org.apache.catalina.loader.Reloader missing from catalina.jar

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: Deleting old TC builds

+1 Remy Maucherat wrote: At the request of infrastructure folks (HD is full ...), I am removing old Tomcat builds. This include older TC 4.1.x releases (< 4.1.10), as well as all non stable TC 4.0.x builds. I'd like to also: - Remove all 4.1.x builds except builds between 4.1.18 and 4.1.26 (4

DO NOT REPLY [Bug 10026] - manager/stop and manager/remove

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: [5.0] [PROPOSAL] Make output buffer size limit configurable

Marc, It can also be useful if you have a client that doesn't support "chunked encoding" - which is probably true for a _lot_ of scripting tools. If there is any other way to have the response not use chunked encoding, then I agree this is not needed. Do we still support HTTP/1.0 or some request h

RE: Deleting old TC builds

Howdy, +1. There will always be users with old versions, but if they lose their original they either have to update to the latest stable release on that branch or get their old version elsewhere. Yoav Shapira Millennium ChemInformatics >-Original Message- >From: Remy Maucherat [mailto:

Deleting old TC builds

At the request of infrastructure folks (HD is full ...), I am removing old Tomcat builds. This include older TC 4.1.x releases (< 4.1.10), as well as all non stable TC 4.0.x builds. I'd like to also: - Remove all 4.1.x builds except builds between 4.1.18 and 4.1.26 (4.1.10 and 4.1.12 Stable ha

DO NOT REPLY [Bug 21617] - Form-based authentication problem on server with non-standard hostname

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 21617] New: - Form-based authentication problem on server with non-standard hostname

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 20406] - Truncated Uploaded File

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 21616] New: - Upload fails under iis5-jk2 and not under tomcat alone

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 21611] - NullPointerException in CoyoteRequestFacade.getSession(

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 21611] - NullPointerException in CoyoteRequestFacade.getSession(

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 21611] - NullPointerException in CoyoteRequestFacade.getSession(

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 21610] - NullPoinyter

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 21611] New: - NullPointerException in CoyoteRequestFacade.getSession(

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 21610] - NullPoinyter

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 21610] New: - NullPoinyter

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: [5.0] [PROPOSAL] Make output buffer size limit configurable

Let's be nice to each other, Remy. I want to help. My question was very specific. Why, when I check out TOMCAT_4_1_24, does it not match what's in your jakarta-tomcat-4.1.24-LE-jdk14.zip source bundle? The bugzilla #'s aren't closed, but I want to be sure these fixes are already in, and provi

Re: [5.0] [PROPOSAL] Make output buffer size limit configurable

David Wood wrote: Speaking of jasper, I'm very sorry to interrupt again, and I know it's bad etiquette to repeat myself, but I have two patches to outstanding bugs in Jasper and I'm just asking for a little help navigating your CVS repository so I can make it easy for you to get them in. Deta

Re: [5.0] [PROPOSAL] Make output buffer size limit configurable

Speaking of jasper, I'm very sorry to interrupt again, and I know it's bad etiquette to repeat myself, but I have two patches to outstanding bugs in Jasper and I'm just asking for a little help navigating your CVS repository so I can make it easy for you to get them in. Details here: http://w

cvs commit: jakarta-tomcat-connectors/jk HOWTO-RELEASE

glenn 2003/07/15 05:27:35 Modified:jk HOWTO-RELEASE Log: Only include those files in jk/conf for mod_jk 1.2 Revision ChangesPath 1.5 +6 -3 jakarta-tomcat-connectors/jk/HOWTO-RELEASE Index: HOWTO-RELEASE ===

mod_jk 1.2.5 release

I have taken care of the serveral minor bug fixes I wanted to get into the mod_jk 1.2.5 release. But I still have the question below about endpoint caching. I would like to renable endpoint caching for use by threaded servers. Is there any reason to not do this? Regards, Glenn Glenn Nielsen wr

cvs commit: jakarta-tomcat-connectors/jk/native CHANGES.txt

glenn 2003/07/15 05:16:19 Modified:jk/native CHANGES.txt Log: Update changes Revision ChangesPath 1.16 +11 -1 jakarta-tomcat-connectors/jk/native/CHANGES.txt Index: CHANGES.txt === RCS fil

cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0 mod_jk.c

glenn 2003/07/15 05:16:06 Modified:jk/native/apache-2.0 mod_jk.c Log: Fix double open of mod_jk.log for apache 2 Revision ChangesPath 1.81 +2 -1 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c Index: mod_jk.c

cvs commit: jakarta-tomcat-connectors/jk/native/common jk_lb_worker.c

glenn 2003/07/15 05:15:42 Modified:jk/native/common jk_lb_worker.c Log: Remove unnecessary error mesage when all lb workers fail Revision ChangesPath 1.13 +2 -1 jakarta-tomcat-connectors/jk/native/common/jk_lb_worker.c Index: jk_lb_worker.c

cvs commit: jakarta-tomcat-connectors/jk/native/common jk_ajp_common.c

glenn 2003/07/15 05:15:18 Modified:jk/native/common jk_ajp_common.c Log: Add worker name to tomcat connection failure error message Revision ChangesPath 1.37 +3 -3 jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c Index: jk_ajp_common.c ===

[ANN] Tomcat 5.0.4 Alpha released

Tomcat 5.0.4 Alpha is now available for testing. Please refer to the changelog included in the release for the list of changes. Downloads: http://jakarta.apache.org/builds/jakarta-tomcat/release/v5.0.4-alpha/ Remy - To unsubs

[4.1.26] Build available for testing

After more delays (the server HD is almost full, and 4.1.25 contained a bug breaking HTTP keep-alive), 4.1.26 is now available for testing. The CVS has been tagged with "TOMCAT_4_1_26". Voting on this build will occur on Friday. Downloads: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/rele

DO NOT REPLY [Bug 21597] - NumberFormatException using Siteminder

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

cvs commit: jakarta-tomcat-site/xdocs index.xml

remm2003/07/15 01:27:43 Modified:docs index.html xdocsindex.xml Log: - Update to 5.0.4 Alpha. Revision ChangesPath 1.41 +1 -1 jakarta-tomcat-site/docs/index.html Index: index.html

cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt

remm2003/07/15 01:24:52 Modified:.RELEASE-NOTES-4.1.txt Log: - Update for 4.1.26. Revision ChangesPath 1.76 +5 -1 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt Index: RELEASE-NOTES-4.1.txt ===

Re: [5.0] [PROPOSAL] Make output buffer size limit configurable

Marc Slemko wrote: On Mon, 14 Jul 2003, Jan Luehe wrote: I would have expected it to include a "Content-Length" header. Would you agree? It, umh, can't do that for dynamic content without buffering the whole response since it doesn't know how long it is. Not even that does work, actually. The pro

Re: [5.0] [PROPOSAL] Make output buffer size limit configurable

Jan Luehe wrote: I noticed that if I send a request specifying HTTP/1.0 as the protocol version, and the response exceeds the output buffer, TC returns an HTTP/1.1 response with neither a "Content-Length" nor a "Transfer-Encoding: chunked" header. I would have expected it to include a "Content-Leng