01-25-2017 07:57 AM
I have the Virtual Traffic Manager set up to redirect my virtual server from HTTP to HTTPS. The HTTPS virtual server is set to enable SSL Decryption. Both the HTTP and HTTPS virtual server are using the same pool.
When I have the redirect disabled and use port 80 my application works. When I enable the redirect and go through the port 443 virtual server. My Application gets called, but it looks like Jetty is trying to start up SSL. Though the SSL decrypt is enabled and internal protocol is set to HTTP.
Is there a known cookbook solution to removing all the HTTPS header information I may have missed?
I expected the internal application would not know the difference at this point. Shouldn't it?
My application is not logging anything and I believe it is not starting up. Though Jetty is returning a 401 error when getting data from the https virtual server.
And relatively new at this.