Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 55313 invoked by uid 500); 6 Aug 2001 16:59:38 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 55304 invoked from network); 6 Aug 2001 16:59:38 -0000 Received: from h32.sny.collab.net (HELO icarus.apache.org) (64.208.42.42) by h31.sny.collab.net with SMTP; 6 Aug 2001 16:59:38 -0000 Received: (qmail 95219 invoked by uid 1059); 6 Aug 2001 16:58:10 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Aug 2001 16:58:10 -0000 Date: Mon, 6 Aug 2001 09:58:10 -0700 (PDT) From: "Craig R. McClanahan" X-Sender: craigmcc@localhost To: tomcat Subject: Re: In-Reply-To: <200108060709.f76798605905@mailgate3.cinetic.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Mon, 6 Aug 2001, Zsolt Koppany wrote: > Hi, I could configure and use tomcat-3.2.3 with SSL (standalone). My > question is whether I can check in a servlet whether SSL has been > enabled on the server? What I plan to do: the user comes to a page > (over the port 8080) and when SSL is enabled I want to add an SSL link > that he can switch to SSL login thus he does not have to know the SSL > port number. > There is nothing in the servlet API that lets you find this out. I would suggest adding an initialization parameter to your web app that passes the SSL port number to your servlet. The lack of this port number would be an indication that your "log in through SSL" link should not be created. > Zsolt Craig McClanahan