Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 976 invoked from network); 23 Jan 2003 20:57:36 -0000 Received: from exchange.sun.com (192.18.33.10) by 208.185.179.12.available.above.net with SMTP; 23 Jan 2003 20:57:36 -0000 Received: (qmail 16447 invoked by uid 97); 23 Jan 2003 20:58:31 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 16244 invoked by uid 97); 23 Jan 2003 20:58:30 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 16140 invoked by uid 98); 23 Jan 2003 20:58:29 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3E305707.8050209@galatea.com> Date: Thu, 23 Jan 2003 13:56:39 -0700 From: Lajos Moczar User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Changing URL References: <3E305595.7050707@galatea.com> <003901c2c322$46bbc390$020101c0@wsta02> X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N Good idea. But either way, it is a bad idea 'cause you want to keep 443 as a secure port and not get confused into having users send unencrypted confidential data. I'm curious why he wants to do this ... Lajos Jakarta wrote: > or use a port forward (it's easy with iptables) > > ----- Original Message ----- > From: "Lajos Moczar" > To: "Tomcat Users List" > Sent: Thursday, January 23, 2003 5:50 PM > Subject: Re: Changing URL > > > >>If you call https://www.domain.com you don't have to supply 443 - it is >>understood. Otherwise, you can't do that (except by some rewrite). And >>besides, why? >> >>Lajos >> >> >>Ravindra K. Bhat wrote: >> >>>Hi: >>> >>>How can I replace my www.domain.com:443 with www.domain.com but still >> > use > >>>the same :443 port? >>> >>>Thanks >>>Ravi >>> >>> >>>-- >>>To unsubscribe, e-mail: >> > > >>>For additional commands, e-mail: >> > > >>> >> >>-- >> >> >> >> Lajos Moczar >> ---------------------------------------- >> Open Source Support, Consulting and Training >> ---------------------------------------- >> Cocoon Developer's Handbook >> (www.amazon.com/exec/obidos/tg/detail/-/0672322579) >> >> _ _____ >> / \ / >> /___\ / >> / \ /____ >> >> http://www.galatea.com -- powered by AzSSL >> >> >>-- >>To unsubscribe, e-mail: > > > >>For additional commands, e-mail: > > > >> > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- Lajos Moczar ---------------------------------------- Open Source Support, Consulting and Training ---------------------------------------- Cocoon Developer's Handbook (www.amazon.com/exec/obidos/tg/detail/-/0672322579) _ _____ / \ / /___\ / / \ /____ http://www.galatea.com -- powered by AzSSL -- To unsubscribe, e-mail: For additional commands, e-mail: