On Thu, Jan 8, 2015 at 2:37 AM, Sailaja Gadireddy
sailaja.gadire...@gmail.com wrote:
Now the issue is when I hit the url http://servername:86 and after
providing the credentials, it is redirecting to https://servername:86 and
throwing the below error.
That port is either SSL enabled or it
Eric Covener schrieb:
On Thu, Jan 8, 2015 at 2:37 AM, Sailaja Gadireddy
sailaja.gadire...@gmail.com wrote:
Now the issue is when I hit the url http://servername:86 and after
providing the credentials, it is redirecting to https://servername:86 and
throwing the below error.
That port is
On Thu, Jan 8, 2015 at 8:24 AM, Hendrik Schmieder
hendrik.schmie...@jedox.com wrote:
isn't
https://www.ietf.org/rfc/rfc2817.txt
what Sailaja Gadireddy looks for ?
Could be. I've never seen anyone use it in practice, but I've seen
hundreds of times just using the wrong protocol/port
Hi Team,
We have a set up like Apahce (80,443) redirects the request to Tomcat
(8080) using mod_jk.
The new requirement is to route the request from the same apache to another
tomcat (8090). Hence I made the different config file for apache with
different ports (86,) and different worker
