https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #5 from Christopher Schultz <ch...@christopherschultz.net> --- This is somewhat related to the long-standing request (can't find the enhancement in BZ at the moment) to emit a plain-text error message from a TLS connector that is contacted by a non-TLS client. This is something that Apache httpd does right now and would be nice to have similar support in Tomcat. Many recent changes in the way that TLS has been implemented in Tomcat make the above possible at this point. Once we are able to handle plaintext-over-TLS, it is theoretically possible to be able to use plaintext for the whole conversation. But right now, I'd say that I'm -1 on the idea of providing insecure and secure communications over the same channel, excepting the use-case above, which is *very* helpful for clients who are perhaps connecting to non-standard ports. The HTTP spec had a recent revision, and nobody seems to have thought of putting dual-use channels into the spec. It's just not that hard to configure two separate ports. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
