RE: [users@httpd] 404 error [EXTERNAL]

2021-06-08 Thread Beard, Shawn
More information actually https://my.domain.com/sample/ works using the http connector instead of ajp connector. However this https://my.domain.com/sample With no trailing / redirects to the http://hostname:9080/sample which is the URL of the tomcat http connector. Shawn​ Beard Sr.

RE: [users@httpd] 404 error [EXTERNAL]

2021-06-08 Thread Beard, Shawn
I got it to work but I don’t know why it worked. I changed the BalancerMember to use the http connector instead of the ajp connector. So changed to http://tomcat-hostname:9080 So the question is, why would that matter and why would it work going to webserver directly but not netscaler? We use

Re: [users@httpd] 404 error

2021-06-08 Thread Stefan Eissing
> Am 08.06.2021 um 15:20 schrieb Beard, Shawn : > > We have put Apache behind a Netscaler load balancer. We have the VIP set up > with ssl and it is terminating SSL at the netscaler. The backend webserver is > not SSL. When we go to the https vanity url, we get a 404 error. But when I > go t

[users@httpd] 404 error

2021-06-08 Thread Beard, Shawn
We have put Apache behind a Netscaler load balancer. We have the VIP set up with ssl and it is terminating SSL at the netscaler. The backend webserver is not SSL. When we go to the https vanity url, we get a 404 error. But when I go to webserver directly on using host:port, it works just fine. I

Aw: Re: [users@httpd] Newer Apache does not offer TLS cipher with TLSv1 anymore

2021-06-08 Thread Hildegard Meier
Thanks for your answer, Stefan. So I would suggest to make the documentation of SSLProtocol clear like this: " You need to name the 'highest' protocol and the 'lowest' protocol, and all protocols in between them, without gap. E.g. if You want to support TLSv1.2 and TLSv1.0, you need to set SSL