https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #9 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to romain.manni-bucau from comment #8) > A webservice doesnt have all the "browser" constraints and defaults (where > all comments are right). I think you are introducing a semantic difference where there is none: a web service and a web application are the same thing. The fact that a browser is one kind of client is irrelevant. The point Mark was trying to make (if I may be so bold) was that "the web" (by whatever definition) already recognizes separate official ports for HTTP and HTTPS, so being able to switch protocols on a single port is inappropriate. If you want to multiplex protocols over a single port, use some kind of service out in front of Tomcat that understands how to do that, and leave Tomcat out of it. This is unnecessary complexity for a product like Tomcat. > I used few providers where you were not able to bind any other port than one > in a reliable manner - you can hardcode instead of using the environment > variable for such an additional port but then it can be forbidden or already > used. Also saw cases on AWS where you can only redirect a single port (using > docker as container of your tomcat). Sounds like your suitcase of tools are failing you. AWS itself imposes no such limitations. -- 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
