The browser determine which port it will attempt to connect on by the
protocol portion of the URL.
If you type in something like:
www.mydomain.com
the browser will default to port 80 and will procede in making a
connection to the remote server on the port. Because you did not specify
a protocol, it assumes you mean http
If you type something like this:
http://www.mydomain.com
the browser knows you mean the http protocol and proceeds to make the
connection. You can override the default behavior of course with a
request like this:
http://www.mydomain.com:81
this will obviously direct you to port 81 on the remote server. This
same set of rules apply to other protocols as well:
https:// -> 443
ftp:// -> 21
Unless you specify an alternate port number the browser will choose the
defaults for the specified protocol.
This problem sounds more like it is in the "router". Is this a router or
is it some kind of firewall doing port forwarding. My first suggestion
would be to start looking at your logs on all three machine (router,
http server, https server) and try to figure out where these https
packets are going. A sniffer may help here as well.
If you need to do a redirect from the http server to the https server,
you can do something like this:
<html>
<head>
<meta HTTP-EQUIV="REFRESH" CONTENT="0; URL=https://www.securecat.com";>
<title>Redirecting to Secure Server...</title>
</head>
<body>
</body>
</html>
You can also look at some of the redirect techniques for apache at there
web page.
HTH
Denny
"Richard S. Huntrods" wrote:
>
> Greetings!
>
> Well, the more you learn, the more you know how little you know! <G>
>
> Current status: I have two servers, one with Apache only and one with
> Tomcat only. This is for historic reasons of server load, but serves me
> very well.
>
> The Apache server listens only to port 80. All works well. For
> example, "http://xx.xx.xx.xx/"; calls up the appropriate index.html page.
>
> The Tomcat server now only listens to port 443 - and responds with SSL
> enabled servlets. This also works well. For example:
> "https://yy.yy.yy.yy/"; calls up a secure index.html file, which starts
> the servlets rolling.
>
> NOW, heres the problem. A router directs port 80 to the Apache server
> and port 443 to the Tomcat server. There is a domain name pointing to
> the address of the router. If you type "http://domain.com/";, the Apache
> server properly serves the web page. HOWEVER - if you type
> "https://domain.com/";, you get the infamous "page cannot be displayed"
> message.
>
> How does one direct "https" inquiries to port 443? I thought this would
> work. Who or what interprets "https" as a request on port 443? Must I
> configure the port 80 Apache machine to "hear" requests on port 443 and
> then relay them to the Tomcat box - and if so, how? (which Apache
> config file)
>
> Thanks very much in advance,
>
> -Richard
>
> --
> To unsubscribe: <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
