Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Submitted By: slupton (slupton)
Assigned to: Nobody/Anonymous (nobody)
Summary: Jetty6: Connecting to SSL server using "http" shows garbage
If you attempt to connect to a https port using "http", garbage characters are displayed in the browser (using IE). I am assuming this is part of the SSL handshake. There really should be some sort of error page, and ideally, the possibility of providing a link or redirect to the correct address using "https".
I apologize ahead of time for my lack of expertise in this matter but the
reason I listed this request is that I noticed that a good few sites
(running on Apache Server) seem to be handling this case. For example,
accessing "https://www.yale.edu" with the address "http://www.yale.edu:443"
will display such an error page. Is there some other potential trickery
being involved with these sites that I'm missing?
Comment By: Chris Haynes (chrishaynes)
Date: 2007-04-06 02:40
Logged In: YES
This is nothing to do with Jetty, and Jetty cannot do what you suggest,
since Jetty never even gets to know that there has been a failed attempt to
establish an SSL session. Telling the browser to use HTTP to connect to an
HTTPS port can never work. The fault, and only cure, is in the design of
the web page - the client and server protocols *must* match.