Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 18653 invoked from network); 3 Sep 2002 17:36:09 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Sep 2002 17:36:09 -0000 Received: (qmail 8541 invoked by uid 97); 3 Sep 2002 17:36:40 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 8484 invoked by uid 97); 3 Sep 2002 17:36:39 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 8471 invoked by uid 50); 3 Sep 2002 17:36:39 -0000 Date: 3 Sep 2002 17:36:39 -0000 Message-ID: <20020903173639.8470.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 12249] - tomcat binds to IP addresses it is configured not to bind to X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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_bug.cgi?id=12249 tomcat binds to IP addresses it is configured not to bind to ruvinsky@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From ruvinsky@yahoo.com 2002-09-03 17:36 ------- Remy, I hope you don't mind that I reopen this bug, for my reasoning below. In a separate email thread, I believe you mentioned that the Coyote connector is NOT supported/recommended for Tomcat 4.0.4, and to stick with HttpConnector when running 4.0.4 in a production environment. If Tomcat binds to any IP address, regardless of what it is configured to do, this sounds like a major [security] problem -- perhaps one that the solution for shouldn't be to just use the newer [non-production quality] Tomcat 4.1.x. Graham, can you specify how to reproduce the problem? Also, what Connector settings do you have in your server.xml? Perhaps I or someone else can look into what the bug is exactly and post a patch? Thanks, Eddie -- To unsubscribe, e-mail: For additional commands, e-mail: