DO NOT REPLY [Bug 32141] - memory leak in jk1.2 with tomcat-5.0.27,apache 1.3.31

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32141] - memory leak in jk1.2 with tomcat-5.0.27,apache 1.3.31

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://issues.apache.org/bugzilla/show_bu

Bug report for Tomcat 4 [2004/12/06]

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

Bug report for Watchdog [2004/12/06]

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

Bug report for Tomcat 3 [2004/12/06]

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

HTTP headers and end of response, reposted for better reading

Hi all, (repost for better reading) I am working at an inplementation of RFC2671 Digest Authentication. I want to do the authentication in my servlet application because I need additional data with the userid and password. For reasons of session management and security I should be able to send

DO NOT REPLY [Bug 32317] - Making mod_jk replication aware (Clustering Support)

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://issues.apache.org/bugzilla/show_bu

Re: Annoyance in the deployer

Bill Barker wrote: Hi, Not something major, but there's that in the deployer: // Make sure there is an application configuration directory // This is needed if the Context appBase is the same as the // web server document root to make sure only web ap

Re: tomcat 5.0.29 and request.getScheme

Thanks for your response. I have test Tomcat with secure="trust" and I have got a proxy error response. This is the configuration directives from apache where proxypass is done: ... ProxyPassReverse /formae http://127.0.0.1:9080/formae RewriteRule ^/formae(.*) http://127.0.0.1:9080/formae$1 [P,L]

Re: tomcat 5.0.29 and request.getScheme

Hey,, please use secure="true" Don't forget to create the Server keystore. Please read the Connector docs: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/ssl-howto.html http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html Regards Peter Luis Fernando Pardo schrieb: Hello, I have ju

tomcat 5.0.29 and request.getScheme

Hello, I have just upgraded my tomcat version from 5.0.16 to 5.0.29 and I have found a problem with the request.getScheme method. I have set apache server to listen on 443 port (SSL) and proxypass to Tomcat on local address (127.0.0.1) and port 9080. This is the connector configuration in Tomca