I agree with Vivek. With an URL in the format:
<protocol>://<hostname>:<port>
The browser will use <protocol> to connect to <hostname> on <port>. If you
don't specify <port>, then the browser will pick the default <port> for
<protocol>, but if the server is not serving the specified <protocol> on the
default <port>, you won't get <anywhere>.
> From: Vivek Khera <[EMAIL PROTECTED]>
> Organization: Khera Communications, Inc., Rockville, MD
> Newsgroups: ml.apache.modperl
> Date: 11 Jul 2001 15:17:11 -0400
> To: [EMAIL PROTECTED]
> Subject: Re: detecting ssl
>
>>>>>> "IG" == Issac Goldstand <[EMAIL PROTECTED]> writes:
>
> IG> Not necessarily. I could easily set up any virtualhost on port
> IG> 443 which will be accessable by https://nasty.servername/ but
> IG> will, in reality, not necessarily be over a secure connection.
>
> I think you've never actually tried this. You will not get the page
> because the client is expecting SSL and you're not providing it. Try
> it. Go ahead, try it.
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Vivek Khera, Ph.D. Khera Communications, Inc.
> Internet: [EMAIL PROTECTED] Rockville, MD +1-240-453-8497
> AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
>
