The only reason that I ask is because the Apache HTTP server does not
behave in this fashion; when I access http://:443 I get a
400 Bad Request error code as expected.
Is there anyway to configure Tomcat to yield a 400 Bad Request error
code if a user attempts to access the SSL port via http ?
dreau
-Original Message-
From: David Smith [mailto:[EMAIL PROTECTED]
Sent: Friday, January 06, 2006 7:53 AM
To: Tomcat Users List
Subject: Re: accessing port 8443 with http
Because port 8443 in your setup is using SSL. The HTTPS protocol and
HTTP protocol start out negotiation in
Because port 8443 in your setup is using SSL. The HTTPS protocol and
HTTP protocol start out negotiation in very different ways. I'm sure to
the average browser it looks like it's receiving a binary stream when in
fact the negotiation starts out with the server sending it's public key
certifi
I have a Tomcat 5.5.9 web application server running on a webserver
listening on port 8443.
Why is it that when I access http://:8443, I am
prompted to download a file of the format application/octet-stream
from any browser from any platform?
If I access https://:8443, I see the tomcat home pag
