element using transport- guarantee confidential.
to the difference in scheme.
Post by Ron Reynoldsoh yeah, you need something listening on port 443 since that's the
default https port if you have direct browser-server communication (all our
LBs handle the HTTPS/certs so it's all http internally - i always forget
about that part). :)
On Monday, November 11, 2013 5:27 PM, Robert Kuhar <
Its not so much your Servlet that cares HTTPS vs HTTP, its the Servlet
Runner. If you are Tomcat you do one bit of configuration to turn on an
HTTPS "listener" for lack of a better name. If you are Jetty, you do
something slightly different. Most bigger scale web-app architectures,
where there are LoadBalancers or a CDN sitting in front of your webapp, the
typical dance is to strip off HTTPS at that point and forward the requests
along to the app servers plain-jane HTTP.
Hi,
My Servlet extends javax.servlet.http.HttpServlet.
Is there anything special for the servlet to support https ?
Thanks